Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Tatuya Kamada
gitlab-ce
Commits
7121b4a4
Commit
7121b4a4
authored
Sep 19, 2014
by
Sytse Sijbrandij
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Warn about restoring to the same version.
parent
eb764b1b
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
1 deletion
+3
-1
doc/raketasks/backup_restore.md
doc/raketasks/backup_restore.md
+3
-1
No files found.
doc/raketasks/backup_restore.md
View file @
7121b4a4
...
...
@@ -6,8 +6,8 @@
A backup creates an archive file that contains the database, all repositories and all attachments.
This archive will be saved in backup_path (see
`config/gitlab.yml`
).
The filename will be
`[TIMESTAMP]_gitlab_backup.tar`
. This timestamp can be used to restore an specific backup.
You can only restore a backup to exactly the same version of GitLab that you created it on, for example 7.2.1.
```
# omnibus-gitlab
...
...
@@ -55,6 +55,8 @@ If you have a manual installation please consider backing up your gitlab.yml fil
## Restore a previously created backup
You can only restore a backup to exactly the same version of GitLab that you created it on, for example 7.2.1.
```
# omnibus-gitlab
sudo gitlab-rake gitlab:backup:restore
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment