Show More
@@ -0,0 +1,42 b'' | |||
|
1 | .. _restore-deleted-repositories: | |
|
2 | ||
|
3 | Restoring Deleted Repositories | |
|
4 | ============================== | |
|
5 | ||
|
6 | By default when repository or whole repository group is deleted an archived copy | |
|
7 | of filesystem repositories are kept. You can see them as special entries in the | |
|
8 | repository storage such as:: | |
|
9 | ||
|
10 | drwxrwxr-x 3 rcdev rcdev 4096 Dec 4 2017 rm__20171204_105727_400795__ce-import | |
|
11 | drwxrwxr-x 6 rcdev rcdev 4096 Nov 21 2017 rm__20180221_152430_675047__svn-repo | |
|
12 | drwxr-xr-x 7 rcdev rcdev 4096 Mar 28 2018 rm__20180328_143124_617576__test-git | |
|
13 | drwxr-xr-x 7 rcdev rcdev 4096 Mar 28 2018 rm__20180328_144954_317729__test-git-install-hooks | |
|
14 | ||
|
15 | ||
|
16 | Data from those repositories can be restored by simply removing the | |
|
17 | `rm_YYYYDDMM_HHMMSS_DDDDDD__` prefix and additionally only in case of Mercurial | |
|
18 | repositories remove the `.hg` store prefix.:: | |
|
19 | ||
|
20 | rm__.hg => .hg | |
|
21 | ||
|
22 | ||
|
23 | For Git or SVN repositories this operation is not required. | |
|
24 | ||
|
25 | After removing the prefix repository can be brought by opening | |
|
26 | :menuselection:`Admin --> Settings --> Remap and Rescan` and running `Rescan Filesystem` | |
|
27 | ||
|
28 | This will create a new DB entry restoring the data previously removed. | |
|
29 | To restore OLD database entries this should be done by restoring from a Database backup. | |
|
30 | ||
|
31 | RhodeCode also keeps the repository group structure, this is marked by entries that | |
|
32 | in addition have GROUP in the prefix, eg:: | |
|
33 | ||
|
34 | drwxr-xr-x 2 rcdev rcdev 4096 Jan 18 16:13 rm__20181130_120650_977082_GROUP_Test1 | |
|
35 | drwxr-xr-x 2 rcdev rcdev 4096 Jan 18 16:13 rm__20181130_120659_922952_GROUP_Docs | |
|
36 | ||
|
37 | ||
|
38 | ||
|
39 | .. note:: | |
|
40 | ||
|
41 | RhodeCode Tools have a special cleanup tool for the archived repositories. Please | |
|
42 | see :ref:`clean-up-cmds` |
General Comments 0
You need to be logged in to leave comments.
Login now