Moving articy:server to another machine

Tue 11. Nov 2014, 15:47

You should read the following before starting the migration!

Depending on your configuration there may be some points to skip or file-paths to change.

On the old machine:
  • Ensure that all users have unclaimed all their partitions
  • Log in to the server management and unregister your license.
  • Stop the Articy Server windows service.
  • Go to the articy:server installation directory and make a full backup of the folder called db. This folder contains the user/project meta data database and the repository of the internal SVN server with project data (if you use that)
  • If you have changed articyserver.cfg or clientsettings.xml in the server directory, you should also backup those files.

On the new machine:

  • Install articy:server (you should not provide the license key in the installer)
  • Stop the Articy Server windows service
  • If you used clientsettings.xml, replace the file with the one from the old machine.
  • If you used articyserver.cfg replace or merge the file with the one from the old machine. (Depending on installation paths you might need to modify/merge the file and can not simply replace it)
  • Delete the db directory and completely replace it with the backup from the old machine.
  • Start the Articy Server windows service.
  • Log in as ServerAdmin (using your current password from the old machine)
  • Register your license key on the new machine.
  • You should now be able to see all your projects and users.
  • If either the articy:server or the internal SVN is externally exposed remember to update the firewall rules to route incoming data to the new machine. (The windows firewall on the new machine has already incoming rules created from the installer)
  • If you do not use the internal SVN and the SVN server has not moved you should be fine now.
  • If you use the internal SVN and do not expose it externally, let your users remove their project folder and open the desired project. This is required since SVN working copies remember the servers they got the data from. (Experienced users can use the svn relocate command instead, Tortiose SVN is a good UI tool for doing so.)
  • By default the internal SVN reports the local machine name and the domain of the server as its full qualified base URL. If you require to have another name you should use the -svn.machinename <internal SVN Domain> switch in the articyserver.cfg. Ensure that this name is properly resolved to the right machine
User avatar
[Articy] Peter Sabath
Articy Staff
Articy Staff
Posts: 89
Joined: Wed 23. Nov 2011, 13:58
Location: Bochum

Return to Knowledge Base

Who is online

Users browsing this forum: No registered users and 3 guests

Who We Are
Contact Us
Social Links