89a407dc3b
Pool repositories are persisted in the database, and when the DB is restored, the data need to be restored on disk. This is done by resetting the state machine and rescheduling the object pool creation. This is not an exact replica of the state like at the time of the creation of the backup. However, the data is consistent again. Dumping isn't required as internally GitLab uses git bundles which bundle all refs and include all objects in the bundle that they require, reduplicating as more repositories get backed up. This does require more data to be stored. Fixes https://gitlab.com/gitlab-org/gitaly/issues/1355 |
||
---|---|---|
.. | ||
backup_hrz.png | ||
backup_restore.md | ||
check.md | ||
cleanup.md | ||
features.md | ||
import.md | ||
list_repos.md | ||
maintenance.md | ||
README.md | ||
user_management.md | ||
web_hooks.md |
comments |
---|
false |
Rake tasks
- Backup restore
- Check
- Cleanup
- Features
- LDAP Maintenance
- General Maintenance and self-checks
- User management
- Webhooks
- Import of git repositories in bulk
- Rebuild authorized_keys file task for administrators
- Migrate Uploads