Restore best practices for scm-manager?

Issue #265 resolved
created an issue

We have successfully updated scm-manager from 1.14 to 1.20 on our DEV instance. We plan on performing this on our PROD instance within the next week. We would like to prepare in case we have issues during or after the upgrade. Are there any recommendations for restoring from a backup, or reverting back to our previous version of scm-manager? We are using the webapp installed on Linux version 2.6.32-220.13.1.el6.x86_64 virtual server.

Comments (6)

  1. Stephan Christann

    Hello jdc2060,

    we backup the webapp folder an the scm-manager home. In our case this is:

    /usr/share/tomcat6/.scm (this is where scm config an repositories are) /var/lib/tomcat6/webapps/scm (folder of the web application)

    I think this should be sufficient for restoring the web app and the data of the repositories.

  2. Sebastian Sdorra repo owner

    The data format of scm-manager has not changed since version 1.2. That means you can just stop the new version and start the old one. The only part which you have to be careful, are the plugin. If you install plugin or upgrade plugins and they are not compatible with your old version, you have to restore the plugins folder.

  3. jdc2060 reporter

    (Reply via

    Looks like I'll be backing up the following in our environment:

    /usr/local/app_root/scm (webapp dir) /usr/local/app_data/.scm (scm config and repo's)

    When we performed the upgrade on our dev instance, I stopped tomcat, removed the old 1.14 war, added the new 1.20 war, and started tomcat. Then I had edit the file to point to the /usr/local/app_data/scm dir. This seemed to pick up all of our old configs, but is this the correct way to upgrade? Please forgive my ignorance on this, as the person who originally set this up is no longer at our company and I want to make sure I'm not missing anything.

    On Wed, Oct 17, 2012 at 1:55 AM, Stephan Christann wrote:

  4. Stephan Christann

    Hello Jjdc2060,

    I think you have just done well. In our case we have no custom directories, so we just have to deploy the new version. If you want to avoid the correction of the directories in the future, i suggest using links to match the suggested folder structure,

  5. Log in to comment