# git clone assume you already have a running Redmine on the New machine with a virgin database. ![]() Let's clone the backup repo to the new box. You should be root, have a passphrase-less ssh-key, stored on the GitServer backup machine in /home/git/.ssh/authorized_keys. Redmine's email config should be simply copied from Old the New. You could even use git-bisect.īefore the migration, the last backup from the old machine is available on GitServer. The advantage of the git-repo is that you can go back to the last correct version even if you notice a corruption 2 weeks too late. It gets database-name, MySQL username and password from the database.yml file.īesides the database, the uploaded files are saved too, see the FILES variable for their location.Īfter dumping the database to redmine.sql and copying the files to /root/redmine/ they are all committed to the git repo which, in turn is pushed to the backup-box (GitServer). Redmine_bak is called every midnight by cron without parameters, which means back-up. On the Old Redmine machine: We assume its root has a passphrase-less ssh-key, and his public key is stored on the GitServer backup machine in /home/git/.ssh/authorized_keys. We need a bare git repo for ~ $ mkdir redmine.git & cd redmine.git & git -bare init We have a third backup machine called GitServer which has a simple github service represented by the git user. ![]() The executable (chmod +x) script is called redmine_bak, residing in /root/redmine/ along with a git-repo. The answer can be found mainly in my well commented Redmine backup-script which can also restore data from backup. How to move your Redmine data to another machine with a newer Redmine version? Machine
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |