History

Zeger-Jan van de Weg 89a407dc3b Restore Object Pools when restoring an object pool 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		2018-12-13 09:00:03 +01:00
..
README.md	port the object storage to CE	2018-03-01 10:34:30 -05:00
backup_hrz.png	Compress all PNG images under doc/	2018-08-27 15:52:03 +02:00
backup_restore.md	Restore Object Pools when restoring an object pool	2018-12-13 09:00:03 +01:00
check.md	…
cleanup.md	Clean orphaned files in object storage	2018-08-07 12:51:58 +02:00
features.md	Docs: fix duplicate titles	2018-05-09 16:11:28 +00:00
import.md	Improve wording and consistency	2018-11-07 16:50:04 -08:00
list_repos.md	…
maintenance.md	…
user_management.md	Resolve "Rename the `Master` role to `Maintainer`" Backend	2018-07-11 14:36:08 +00:00
web_hooks.md	Fix gitlab:web_hook tasks	2018-12-06 18:37:05 +00:00

comments
false

Rake tasks