/usr/local/sbin/auto-gitlab-backup/auto-gitlab-backup.sh: line 101: gitlab-ci-rake: command not found

for testing ssh and rsync operations, create a testing mode that skips the rake operations and goes directly to rsync functions. Maybe also some debugging and printing variables.

Hi, first of all, i want to thank you for this helpful script!
It works fine manually but each time I launch your script with "/usr/local/sbin/auto-gitlab-backup/auto-gitlab-backup.sh", it asks me the remote ssh password.
In fact, I can't find option in "auto-gitlab-backup.conf" which refers to remote password. Is it "rsync_password_file"?
Thanks

Need a way to test certain features. other than 'dry-run'

http://doc.gitlab.com/ce/raketasks/backup_restore.html#for-omnibus-installations

Determine if any benefit to "CRON=1" in our call to backup.

root ᐅ varina → /var/opt/gitlab/ci-backups ᐉ  gitlab-ci-rake backup:create
Applying final database migrations ... 
done
Dumping database ... 
Dumping PostgreSQL database gitlab_ci_production ... [DONE]
done
Dumping builds ... 
tar: /var/opt/gitlab/gitlab-ci/builds: Cannot chdir: Permission denied
tar: Error is not recoverable: exiting now
done
Creating backup archive: 1453914753_gitlab_ci_backup.tar ... done
Uploading backup archive to remote storage  ... skipped
Deleting tmp directories ... done
done
done
Deleting old backups ... done. (0 removed)


Your final CI export is in the following file:

-rw-r--r-- 1 gitlab-ci gitlab-ci 90K Jan 27 12:12 /var/opt/gitlab/ci-backups/1453914753_gitlab_ci_backup.tar

Directory permissions to restrictive for root to access:

ll /var/opt/gitlab/gitlab-ci
total 32
drwx------ 4 git       git        4096 Oct  1 15:18 builds

Manually fix:

sudo chown -R git:root /var/opt/gitlab/gitlab-ci/builds/
sudo chmod -R g+rwx /var/opt/gitlab/gitlab-ci/builds/

Wait and see if the next upgrade fixes/breaks things.

wrap some b2 commands. will require b2 being manually installed and setup with root user access to b2 account config file.

fix in readme:

5 5 * * * /usr/local/sbin/autogitbackup/auto-gitlab-backup.sh 

to show real path

last import hooks were wrong and no updates in imported repos were notes on Dashboard.

Might just 'borrow' code as for installs with custom git home, it will fail.

after syncing run quota command to see available diskspace.

ex:

ssh [email protected] quota

===== Archiving Configs =====
Local config backup aren't enabled or /var/opt/gitlab/backups/configBackups is not writable.

permissions change on folder overtime gitlab is updated. find a work around or other location for backups.

as it is more integrated now.

This just adds "CRON=1" to the rake command.

Have following elements based on features available:

icons to show:

• repo backup
• config backup
• remote copy (rsync)

rsync Problem
(1)use custom Port;
(2)server url should be “$remoteUser@$remoteServer::$remoteDest”

rsyncUp() {

rsync up with default key

echo =============================================================
echo Start rsync to rsync.net/backup no key
echo =============================================================
#rsync -Cavz --delete-after /$gitRakeBackups/ $remoteUser@$remoteServer:$remoteDest
rsync -Cavz --port=$remotePort --password-file=$rsync_password_file --delete-after /$gitRakeBackups/ $remoteUser@$remoteServer::$remoteDest

}

root@gitlab backups]# cat /opt/gitlab/embedded/service/gitlab-rails/VERSION
11.11.4
[root@gitlab backups]# ll
total 227840
-rw------- 1 git git 233308160 Jul 11 17:45 1562838333_2019_07_11_11.11.4_gitlab_backup.tar

[root@ELK-SZ-03 backups]# cat /opt/gitlab/embedded/service/gitlab-rails/VERSION
11.11.4
[root@ELK-SZ-03 backups]# gitlab-rake gitlab:backup:restore BACKUP=1562838333_2019_07_11_11.11.4_gitlab_backup.tar
The backup file 1562838333_2019_07_11_11.11.4_gitlab_backup.tar_gitlab_backup.tar does not exist!

Maybe a fuse mounted fs or a NFS mount

hi there

Great script thanx!!! is there a way to automate the ssh password, as currently i need to add the remote dir ssh password before it cab copy the backup to the remote dir. So cant run it automatically

http://doc.gitlab.com/ce/raketasks/backup_restore.html#omnibus-installations

Merge omnibus and the regular master branch so that it doesn't matter which instal (omnibus or other) is used, the master branch is production.

When trying to make the backup it tries to open this folder:
du: cannot access /var/opt/gitlab/gitlab/tmp/backups': No such file or directory
`

and the folder should be /var/opt/gitlab/backups

To fix that gitlabHome and gitRackeBackups should have this values:
gitlabHome="$gitHome/" gitRakeBackups="$gitlabHome/backups"

This is from the omnibus-master branch.

Here's my configuration:

remoteUser="ada" #user account on remote server
remoteServer="ada-datanode4" #remote host
remoteDest="/home/ada/gitlab_backup" #remote path
sshKeyPath="" #path to an alternate ssh key, if needed.
remotePort=22 # ssh port or 873 for rsyncd port
## Only change the below setting if you have git's home in a different location
gitHome="/var/opt/gitlab"
## only set below if rvm is in use and you need to source the rvm env file
# echo $(rvm env --path)
RVM_envPath=""
## only use the below settings if your destination is using rsync in daemon mode
remoteModule=""
rsync_password_file=""
checkQuota="" #change to true or 1 to enable

I've ssh-copy-id so I thought there's no need to use password, but when I ran auto-gitlab-backup.sh it always asking me for password.

Deleting old backups ... skipping
===== Sizing =====
Total disk space used for backup storage..
Size - Location
3.0G /var/opt/gitlab/backups

=============================================================
Start rsync to
ada-datanode4:/home/ada/gitlab_backup
default key

ada@ada-datanode4's password:

How to solve this problem?
Another question, the backup_keep_time setting only affect backup files in local machine, but backup files transfered to remote server will not be affected, correct?

Really liking this script, saved me sooo much time trying to figure out bash and rsync. A++++ :)

Only little issue I seem to have is in regards to the config backups. I have configured the script to also automate and move backing up the gitlab configuration, this works brilliantly. I followed the default way of having a configBackups directory within the main Gitlab backups folder. The backups work and are copied over to my other machine via rsync. However, the names of these backups are not kept. The names of the main rake backups are kept though. I thought maybe it was because there was a space in the file names, but this wasn't the case.

For example a backup created today would have the name of gitlabConf-17-05-03 21:27:30. The file on the Gitlab server is correctly named. However, after the transfer on the second server it is instead called GR05BW~T.TGZ

I know very little about rsync so is this some kind of configuration that needs to be done with this? Are you able to reproduce this? Seems strange considering the main backups are working.

When i set quietRake=1 option in the configuration file, it is simply ignored and rake still prints lots of debug messages. After a quick research it turned out that the rake command is generated before the configuration file is actually loaded. The fix seems to be very simple, look at my patch which solves the issue for me:

diff --git a/auto-gitlab-backup.sh b/auto-gitlab-backup.sh
index 0faddad..d50f67a 100755
--- a/auto-gitlab-backup.sh
+++ b/auto-gitlab-backup.sh
@@ -41,12 +41,6 @@ gitlab_rails="/opt/gitlab/embedded/service/gitlab-rails"
 PDIR=$(dirname $(readlink -f $0))
 dateStamp=`date +"%F %H:%m:%S"`
 confFile="$PDIR/auto-gitlab-backup.conf"
-if [[ $quietRake == 1 ]]
-then
-  rakeBackup="gitlab-rake gitlab:backup:create CRON=1"
-else
-  rakeBackup="gitlab-rake gitlab:backup:create"
-fi

 ###
 ## Functions
@@ -95,6 +89,14 @@ archiveConfig() {
 rakeBackup() {
     echo ===== raking a backup =====
     cd $gitRakeBackups
+
+    if [[ $quietRake == 1 ]]
+    then
+      rakeBackup="gitlab-rake gitlab:backup:create CRON=1"
+    else
+      rakeBackup="gitlab-rake gitlab:backup:create"
+    fi
+
     $rakeBackup
 }

Anyway, thank you for a useful script. It saves me a lot of time!

to prevent unintended errors.

Hey there,

I'm wondering if it's possible to enable a option to disable the delete feature on the backup server end? This is because I'd like to have the backups on my gitlab server be deleted once they're a week old but a 6 months old on by backup server end due to space constraints on the gitlab server end.

No confFile found

Add text to say that no remote copy will be done

At the very least compress .tar archives when transferring. Better yet, post .tar creation, compress and replace.

Per https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/backups.md

the /etc/gitlab should also be backed up. Look into a way to back it up.
Also /etc/ssh for host keys

make sure support for gitlab_rails['backup_path'] = '/mnt/backups' exists currently.

also would be nice to remove color formatting

For 7.11.x make an option to backup gitlab-ci