diff options
author | Job van der Voort <job@gitlab.com> | 2015-05-26 07:22:38 +0000 |
---|---|---|
committer | Job van der Voort <job@gitlab.com> | 2015-05-26 07:22:38 +0000 |
commit | 109a3684f0775cbb3dbb709b0494ca6ebae0ae3c (patch) | |
tree | ce284ca124dd893187afa91e5e96b1909751257e | |
parent | 8bed55d247367cb7c6ed0e68a40745ff3bcaaec9 (diff) | |
parent | 2b4eb7869edec4db1eb4022800899c7beb0b81ce (diff) | |
download | gitlab-ce-109a3684f0775cbb3dbb709b0494ca6ebae0ae3c.tar.gz |
Merge branch 'backup_gitlab.com' into 'master'
Added note about backups for gitlab.com
Added note about backups for Gitlab.com based on question on Twitter
https://twitter.com/MarcelloLins/status/598544357294272513
See merge request !1828
-rw-r--r-- | doc/raketasks/backup_restore.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index bca4fcfb404..ae2d465e0c1 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -299,3 +299,7 @@ Example: LVM snapshots + rsync If you are running GitLab on a virtualized server you can possibly also create VM snapshots of the entire GitLab server. It is not uncommon however for a VM snapshot to require you to power down the server, so this approach is probably of limited practical use. + +### Note +This documentation is for GitLab CE. +We backup GitLab.com and make sure your data is secure, but you can't use these methods to export / backup your data yourself from GitLab.com.
\ No newline at end of file |