<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Currently the backup task only clears production DB when restoring. The Praefect database gets over written only for the repositories that get restore. See [slack discussion](https://gitlab.slack.com/archives/C3ER3TQBT/p1665509772839789) When there are more repositories on the DB than being restore, this can cause issues when creating new projects. See [zd-294970](https://gitlab.zendesk.com/agent/tickets/294970) The proposal is to wipe Praefect DB and storage prior to restoring repositories. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->