dosire/gitlabhq — pull request #96 by maxlazio (2012-12-04 12:46:51+00:00)
Title: Add a warning to the task.

There are couple of problems with the current backup.rake task.

* Backing up of the repositories doesn't take all files from the repository. If you try to restore repositories from the backup couple of files will be missing which will prevent a user from using the repository. For example, gl-conf is not backed up and after the project is restored from backup and git push attempted error

```
split conf set, gl-conf not present for REPO
```
will halt the attempted push. One solution is to backup the whole git/repositories directory by copying the whole directory.

* Attachments are not backed up. If there is a discussion in an issue that contains comments with attached files, after restore those attachments would be lost. This is a problem because it can harm the workflow established in the issue.
* Gitlab user ssh key is not backed up. After the backup is restored everyone who pushed to the repository would get a warning/failure about the host key change that would prevent them from pushing. Even though this problem is solved by removing the host from known_hosts on clients machine it can still be a problem in larger organizations.

These are the problems that I've encountered while restoring the backup. I don't know if there are other problems but I do feel that a disclaimer of some sort needs to be added to the task. Something that would warn users that this rake task is not a complete backup solution and that they need to consider backing up other files as well.