<p>As <a href="https://devops.stackexchange.com/users/13/tensibai">Tensibai</a> mentioned in the comment - better way is backup you Jenkins instance before an update</p>

<p>There are different ways to do this:</p>

<h1>Plugins</h1>

<p>Jenkins has a lot of backup plugins, most popular is:</p>

<p><a href="https://wiki.jenkins.io/display/JENKINS/PeriodicBackup+Plugin" rel="nofollow noreferrer">PeriodicBackup Plugin</a> - be aware, has status <code>This plugin is up for adoption</code> right now, that means there is can be lack of support</p>

<p><a href="https://wiki.jenkins.io/display/JENKINS/thinBackup" rel="nofollow noreferrer">thinBackup Plugin</a> - the same about current status of plugin</p>

<p><a href="https://wiki.jenkins.io/display/JENKINS/SCM+Sync+configuration+plugin" rel="nofollow noreferrer">SCM Sync configuration plugin</a> - see attention on the plugin page, this is deprecated plugin, the suggestion about <strong>migrate their jobs to <a href="https://wiki.jenkins.io/display/JENKINS/Pipeline+Plugin" rel="nofollow noreferrer">Pipeline Plugin</a></strong> and <strong>use the <a href="https://wiki.jenkins.io/display/JENKINS/Configuration+as+Code+Plugin" rel="nofollow noreferrer">Configuration as Code Plugin</a></strong> also make sense</p>

<p>All of them easy to use, also you can <a href="https://plugins.jenkins.io" rel="nofollow noreferrer">discovery any Jenkins plugin here</a></p>

<h1>Your own solution</h1>

<p>Jenkins has good structure for backup, it is not hard to understand what exactly you need to backup and how.</p>

<p>You can write script\job with simple steps <code>copy</code>, <code>archive</code>, <code>move</code> to achieve backup of your Jenkins.</p>

<p>More information and discussion about how to backup jenkins can be found here: <a href="https://devops.stackexchange.com/questions/21/how-do-you-back-up-jenkins-jobs-master-configs">How do you back up Jenkins jobs &amp; master configs?</a></p>

<h2>As for me</h2>

<p>I'm using <code>Periodic Backup</code> plugin + my own scripts for transfering backups into different places. But this plugin is not really stable and has opened issues, so i'm not recommend this for highload production use. That's fine for personal not-critical systems. Now I decided to migrate to my own solution with simple job to archive and copy all configs of my Jenkins instances. </p>

CC BY-SA 4.0
2018-09-19T08:49:12.867Z
2018-09-19T08:49:12.867Z
Sysanin
<p>I would like to upgrade my Jenkins version(From 2.60.2 to 2.121.1) and some of my plugins. Currently, there are some jobs configured in it. I know there are some configuration changes needed for jobs after upgrading the plugins. Is there any way to restore all the settings(data + conf + plugins) to the previous state if my updates went wrong.</p>

CC BY-SA 4.0
2018-06-20T11:58:12.567Z
That's called a backup, and is the first warning in all and every upgrade documentation usually.
Tensibai
<jenkins><jenkins-plugins>
How to revert the Jenkins setup if plugin/Jenkins updates went wrong.
RAISAL PA
# How to revert the Jenkins setup if plugin/Jenkins updates went wrong.

(Asked by: username_0 on 2018-06-20)

I would like to upgrade my Jenkins version(From 2.60.2 to 2.121.1) and some of my plugins. Currently, there are some jobs configured in it. I know there are some configuration changes needed for jobs after upgrading the plugins. Is there any way to restore all the settings(data + conf + plugins) to the previous state if my updates went wrong.

**Tags:** jenkins, jenkins-plugins

> **Comments:**
> **username_1**: That's called a backup, and is the first warning in all and every upgrade documentation usually.  

---

## 1 answers

### Answer by username_2 on 2018-09-19. Score: 2 | Accepted answer

As [username_1](https://devops.stackexchange.com/users/13/tensibai) mentioned in the comment - better way is backup you Jenkins instance before an update

There are different ways to do this:

# Plugins

Jenkins has a lot of backup plugins, most popular is:

[PeriodicBackup Plugin](https://wiki.jenkins.io/display/JENKINS/PeriodicBackup+Plugin) - be aware, has status `This plugin is up for adoption` right now, that means there is can be lack of support

[thinBackup Plugin](https://wiki.jenkins.io/display/JENKINS/thinBackup) - the same about current status of plugin

[SCM Sync configuration plugin](https://wiki.jenkins.io/display/JENKINS/SCM+Sync+configuration+plugin) - see attention on the plugin page, this is deprecated plugin, the suggestion about **migrate their jobs to [Pipeline Plugin](https://wiki.jenkins.io/display/JENKINS/Pipeline+Plugin)** and **use the [Configuration as Code Plugin](https://wiki.jenkins.io/display/JENKINS/Configuration+as+Code+Plugin)** also make sense

All of them easy to use, also you can [discovery any Jenkins plugin here](https://plugins.jenkins.io)

# Your own solution

Jenkins has good structure for backup, it is not hard to understand what exactly you need to backup and how.

You can write script\job with simple steps `copy`, `archive`, `move` to achieve backup of your Jenkins.

More information and discussion about how to backup jenkins can be found here: [How do you back up Jenkins jobs & master configs?](https://devops.stackexchange.com/questions/21/how-do-you-back-up-jenkins-jobs-master-configs)

## As for me

I'm using `Periodic Backup` plugin + my own scripts for transfering backups into different places. But this plugin is not really stable and has opened issues, so i'm not recommend this for highload production use. That's fine for personal not-critical systems. Now I decided to migrate to my own solution with simple job to archive and copy all configs of my Jenkins instances.


---

