summaryrefslogtreecommitdiff
path: root/doc/operations
diff options
context:
space:
mode:
authorJacob Vosmaer <contact@jacobvosmaer.nl>2015-10-05 18:02:32 +0200
committerJacob Vosmaer <contact@jacobvosmaer.nl>2015-10-05 18:02:32 +0200
commite0ef09d9a35bf001acbb89e4177d942f6db93e50 (patch)
treea2be59427459820e35e1070232ba8bb6c805268d /doc/operations
parent6479b821ebc04d9e2ec69be451768968c06ce6a5 (diff)
downloadgitlab-ce-e0ef09d9a35bf001acbb89e4177d942f6db93e50.tar.gz
Some more text in the doc
Diffstat (limited to 'doc/operations')
-rw-r--r--doc/operations/moving_repositories.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/operations/moving_repositories.md b/doc/operations/moving_repositories.md
index 88b90e91316..d156f3ad777 100644
--- a/doc/operations/moving_repositories.md
+++ b/doc/operations/moving_repositories.md
@@ -16,7 +16,10 @@ source and the target.**
## Target directory is empty: use a tar pipe
If the target directory `/mnt/gitlab/repositories` is empty the
-simplest thing to do is to use a tar pipe.
+simplest thing to do is to use a tar pipe. This method has low
+overhead and tar is almost always already installed on your system.
+However, it is not possible to resume an interrupted tar pipe: if
+that happens then all data must be copied again.
```
# As the git user
@@ -43,9 +46,11 @@ If you want to compress the data before it goes over the network
## The target directory contains an outdated copy of the repositories: use rsync
-In this scenario it is better to use rsync. This utility is either
-already installed on your system or easily installable via apt, yum
-etc.
+If the target directory already contains a partial / outdated copy
+of the repositories it may be wasteful to copy all the data again
+with tar. In this scenario it is better to use rsync. This utility
+is either already installed on your system or easily installable
+via apt, yum etc.
```
# As the 'git' user