What issues are you seeing that prevent them from being good for production scale?
From: <[email protected]> on behalf of "[email protected]" <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, November 27, 2018 at 6:49 AM To: Jenkins Users <[email protected]> Subject: Re: Jenkins Backup and Restore Tried out a bunch of them. Unfortunately, none of them are good for a production scale. On Monday, November 26, 2018 at 5:18:04 PM UTC-5, [email protected] wrote: The beauty of Jenkins is that it's NOT built-in, but can be easily added as a plugin (of which there are several). On Monday, November 26, 2018 at 1:41:19 PM UTC-8, [email protected] wrote: I wish for a tool like Jenkins it had a backup and restore option built in. On Monday, November 26, 2018 at 4:35:04 PM UTC-5, john.mellor wrote: I have had restore issues with *ALL* of the backup plugins that I have tried. The problem is that they are using stupid mechanisms to copy the filesystem that cannot correctly copy a symlink. This breaks the LastSuccessfulBuild and LastUnsuccessfulBuild and LastFailedBuild symlinks, causing lots of secondary issues. Doing my own using cpio or rsync in a cronjob only messes up copying very large files that exceed the archive limits (4GB for cpio for instance). On Mon, 2018-11-26 at 21:12 +0000, Artur Szostak wrote: > Just my opinion: but I would forget about the backup plugins in > Jenkins for full production backups. They all do a poor job when it > comes to a full backup for a production system that also needs high > availability. The best that can be done at the moment is to run > Jenkins on a file system or data store that is able to perform copy- > on-write snapshots. From within Jenkins you will want to setup a > simple job that triggers the copy-on-write snapshot when no other job > is running. Then use your normal production backup solutions to > backup the snapshot in the background. > > Cheers > > Artur > > ________________________________________ > From: [email protected] < > [email protected]> on behalf of [email protected] > <[email protected]> > Sent: 01 November 2018 21:36 > To: Jenkins Users > Subject: Jenkins Backup and Restore > > We have a Jenkins instance running and we are trying to setup a > backup and restore mechanism in case of any mishaps. We are looking > for a full backup of the Jenkins and so decided to go with > PeriodicBackup plugin. With this plugin, the backup works > fine. But, we are trying to restore it in a completely new Jenkins > setup and not able to restore. When we pick the backup file that we > want to restore from, it says restoring, but nothing happens. Even > after waiting out for over 30 mins, nothing is restored. As a work > around, I stopped the Jenkins service, renamed the 'JENKINS_HOME' > (/var/lib/jenkins) folder to 'jenkins_backup' and created another > folder called 'jenkins' in the same location. In this folder, I > copied all the files from the backup and then started Jenkins (NOTE: > I didn't change the .owner file. I'm using the .owner file of the > new Jenkins only). Jenkins came up and I was able to see all the > configurations from the old one. Everything was fine. I let it like > that overnight and in the morning when I came and tried to access it, > Jenkins was way too slow and I was not able to save any new > configuration. When I try I'm getting > java.io.ioexception: too many open files jenkins > error. I restarted the jenkins and it's taking too long for the UI > to come up. Am I doing anything wrong here? Any suggestions for my > requirement? > > P.S. - I tried SCMSync plugin and ThinBackup. But, problem with > these are that they don't do full backup. But, with ThinBackup both > backup and restore works fine. > > -- > You received this message because you are subscribed to the Google > Groups "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]<mailto: > [email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/0c58b4fa-4e8b-4c53-9ca9-b99397078fae%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/0c58b4fa-4e8b-4c53-9ca9-b99397078fae%40googlegroups.com?utm_medium=email&utm_source=footer> > ;. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f5625308-1145-4d77-b021-62be8a779592%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/f5625308-1145-4d77-b021-62be8a779592%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/588AA5F3-DCE6-4516-B0C7-7E2C161E3D5C%40godaddy.com. For more options, visit https://groups.google.com/d/optout.
