Share this page
Backup and Restore commands
GitCentric provides two sets of commands for backing up and restoring GitCentric:
full_backup.sh, full_restore.sh
The full_backup.sh command backs up the GitCentric databases, your Git repositories, and your configuration files.
Similarly, full_restore.sh copies all required files to the new location.
Use these commands any time you wish to completely back up GitCentric. You should also use these commands when migrating GitCentric from one server to another.
Note: We recommend that you use the full_backup.sh and full_restore.sh commands to back up and restore GitCentric as described below.
backupdbs, restoredbs
The low-level backupdbs and restoredbs commands, as the names imply, back up and restore only the GitCentric databases. Other important data, like your Git repositories and configuration files are not backed up by the backupdbs command.
backupdbs and restoredbs are kandoMaintain commands. For details, see kandoMaintain Utility.
You might wish to use these commands if your current backup strategy includes a third-party tool for backing up your repositories.
Note: If you are currently using backupdbs and restoredbs to back up GitCentric, you can continue to do so.
Best Practices
We recommend that you back up GitCentric on a daily basis. You can back up GitCentric at any time, but we recommend that you choose a time of light system usage.
Tip: Consider creating a cron job for GitCentric backups. For examples of cron jobs, see Set up Gerrit code review garbage collection.
See also:
