<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=396926) </details> <!--IssueSummary end--> [According to Kibana](https://log.gprd.gitlab.net/app/dashboards#/view/03a11c50-ba46-11ec-b73f-692cc1ae8214), some projects are exported several times in a short period. Since exporting projects consume a lot of resources, we should consider limiting the number of times a project can be exported. For example, there are cases of projects being exported 40 times in a period of 7 days, on average, five exports per day or one every 4 hours. Apparently, users are using Project Export as a disaster recovery tool, and I believe one reason is our [documentation](https://docs.gitlab.com/ee/user/gitlab_com/#backups) recommends using Project Export as a backup solution. However, I don't think the tool was built with such intention at least the [MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/41788) that introduced such information doesn't explain why we decided to suggest Project Export as a backup solution.