summaryrefslogtreecommitdiff
path: root/lib/backup
Commit message (Collapse)AuthorAgeFilesLines
* Replaced config accessDominic Renner2019-03-181-1/+1
| | | | Replaced Settings with Gitlab.config for uniformity
* trim empty lineFrederic Van Espen2019-03-071-1/+0
|
* Merge branch 'master' into incremental-backupsFrederic Van Espen2019-03-073-4/+11
|\
| * Add convenience methods for creating project and Wiki repositoriesStan Hu2019-02-051-1/+1
| | | | | | | | This makes it easier to access other project arguments in the future.
| * Send project name with Gitaly repository requestsStan Hu2019-02-051-1/+1
| | | | | | | | | | | | | | When hashed storage is in use, it's helpful to have the project name associated with the request. Closes https://gitlab.com/gitlab-org/gitaly/issues/1394
| * Modify file restore to rectify tar issueJason Colyer2019-01-171-1/+1
| | | | | | | | | | Fixed typo in run_pipeline! function -> Open3.pieline to Open3.pipeline
| * Modify file restore to rectify tar issueJason Colyer2019-01-171-6/+4
| | | | | | | | | | | | | | Adjusted run_pipeline! function to match rubocop syntax requirements Adjusted run_pipeline! function to use variable instead of string interpolation
| * Modify file restore to rectify tar issueJason Colyer2019-01-171-6/+4
| | | | | | | | | | | | Changed run_pipeline! function to have use $ in regex Changed run_pipeline! function to use Open3.pipeline instead of Open3.pipeline_start
| * Modified files.rb to handle tar errorJason Colyer2019-01-161-2/+12
| | | | | | | | | | | | | | | | Changed the run_pipeline! function to instead use Open3.pipeline_start In doing so, the code is able to grab the last STDERR. In the case where the error is the one from older tar versions (relating to ./), it will not raise a Backup::Error. All other instances of command failure will result in Backup::Error being raised.
| * Add SSE-C key configuration option for Amazon S3 remote backupsPepijn Van Eeckhoudt2019-01-091-0/+1
| |
| * Avoid extra storage bucket perm and querymk/avoid-extra-storage-perm-and-queryMichael Kozono2018-12-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | Specifically, the `ListAllMyBuckets` permission. This works if you know the directory exists. See more: * https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23981 * https://stackoverflow.com/a/12288581/1992201
* | fix option testFrederic Van Espen2019-03-071-1/+1
| |
* | introduce optional rsyncable flagFrederic Van Espen2019-03-073-3/+13
| |
* | fix code styleFrederic Van Espen2018-12-271-5/+5
| |
* | set the --rsyncable option for gzipFrederic Van Espen2018-12-262-3/+3
| |
* | Allow to override part of the backup filenameFrederic Van Espen2018-12-261-1/+5
|/
* Restore Object Pools when restoring an object poolZeger-Jan van de Weg2018-12-131-1/+15
| | | | | | | | | | | | | | | | Pool repositories are persisted in the database, and when the DB is restored, the data need to be restored on disk. This is done by resetting the state machine and rescheduling the object pool creation. This is not an exact replica of the state like at the time of the creation of the backup. However, the data is consistent again. Dumping isn't required as internally GitLab uses git bundles which bundle all refs and include all objects in the bundle that they require, reduplicating as more repositories get backed up. This does require more data to be stored. Fixes https://gitlab.com/gitlab-org/gitaly/issues/1355
* Enable frozen string for lib/gitlab/*.rbgfyoung2018-10-221-1/+1
|
* Add installation type to backup information fileBalasankar "Balu" C2018-10-051-0/+1
|
* Enable frozen string in lib/api and lib/backupgfyoung2018-09-2911-0/+22
| | | | | | | | | | Partially addresses #47424. Had to make changes to spec files because stubbing methods on frozen objects is a mess in RSpec and leads to failures: https://github.com/rspec/rspec-mocks/issues/1190
* Remove feature flags from lib/backupZeger-Jan van de Weg2018-07-311-150/+21
| | | | | | | | | | | | | Moved to OPT_OUT in 7d14b725a0da41d1ae7c0a8496b5e66832023e3b, Now, by removing the feature gates, this is an mandatory feature. Related issues: - https://gitlab.com/gitlab-org/gitaly/issues/526 - https://gitlab.com/gitlab-org/gitaly/issues/1194 Closes https://gitlab.com/gitlab-org/gitaly/issues/749 Closes https://gitlab.com/gitlab-org/gitaly/issues/1212 Closes https://gitlab.com/gitlab-org/gitaly/issues/1195
* Move repo backup RPC's to opt-outgitaly-backup-opt-outJacob Vosmaer2018-06-251-4/+4
|
* Restore custom hooks for wikirestore-custom-hooks-wikiAhmad Hassan2018-06-211-0/+2
|
* Move backup custom hooks up a leveluse-backup-custom-hooks-gitalyAhmad Hassan2018-06-201-4/+2
|
* Output done for wiki and repoAhmad Hassan2018-06-191-14/+3
|
* Migrate repo backup to gitalyAhmad Hassan2018-06-151-43/+80
|
* Merge branch 'use-restore-custom-hooks-gitaly' into 'master'Douwe Maan2018-06-081-10/+23
|\ | | | | | | | | Use RestoreCustomHooks RPC in restore rake task See merge request gitlab-org/gitlab-ce!19370
| * Use RestoreCustomHooks RPC in restore rake taskAhmad Hassan2018-06-071-10/+23
| |
* | Consistently use tar lookup functionJacob Vosmaer2018-06-071-3/+8
|/
* Find and mark more Git disk access locationsJacob Vosmaer (GitLab)2018-06-054-11/+22
|
* Use Gitaly's DeleteAllRepositories RPC during backup restoreJacob Vosmaer (GitLab)2018-05-281-20/+36
|
* Merge branch 'migrate-restore-repo-to-gitaly' into 'master'Douwe Maan2018-05-241-45/+43
|\ | | | | | | | | | | | | Use gitaly repository_service.CreateRepositoryFromBundle to restore (rake task) Closes charts/gitlab#390 See merge request gitlab-org/gitlab-ce!18644
| * Remove unneeded gitaly_migrate functionmigrate-restore-repo-to-gitalyAhmad Hassan2018-05-241-8/+0
| |
| * Take restoring custom hooks and the skip flag out of scopeAhmad Hassan2018-05-231-4/+2
| |
| * Remove gitaly_migrate blocks and replace by early returnAhmad Hassan2018-05-211-33/+26
| |
| * Move restore_custom_hooks to its seperate functionAhmad Hassan2018-05-181-16/+20
| |
| * Return from prepare directory if gitaly skip is enabledAhmad Hassan2018-05-171-0/+2
| |
| * Call path_to_repo only when using gitalyAhmad Hassan2018-05-171-1/+1
| |
| * Link to upstream gitaly issues for the missing restore pathsDJ Mountney2018-05-161-6/+8
| |
| * Fix the paths for wiki restoreDJ Mountney2018-05-151-7/+8
| |
| * Output project name before restoring each project repoDJ Mountney2018-05-151-0/+1
| |
| * Remove hooks restore that is no longer necessaryDJ Mountney2018-05-151-7/+0
| |
| * Add back some of the non-gitaly restore functionality behind gatesDJ Mountney2018-05-151-20/+66
| |
| * Wrap create_from_bundle in a begin rescue blockAhmad Hassan2018-05-151-5/+19
| |
| * Better repo restore progress loggingAhmad Hassan2018-05-151-1/+5
| |
| * Remove useless print lineAhmad Hassan2018-05-151-1/+0
| |
| * Use gitaly repository_service.CreateFromBundle to restoreAhmad Hassan2018-05-151-53/+2
| |
* | Fix backup creation and restore for specific Rake tasksStan Hu2018-05-249-41/+76
|/
* Describe workaround when restore fails because of `Errno::EBUSY`Bob Van Landuyt2018-04-233-0/+18
| | | | | | When `Errno::EBUSY` is raised during restore, this could indicate that the directory being restored into is a mountpoint. In this case we explain the user how to retry the restore.
* Move existing dirs to a temp location while restoreBalasankar "Balu" C2018-03-309-34/+49
| | | | | | | Instead of renaming existing storage directories to a timestamped format, create a timestamped directory in a temporary location and move the individual files and folders inside storage directories to it. This helps us with nested storage directories.
View Lorry Controller Status