VERIFIED SOLUTION i
X

Migrating to a new EngageOne Vault server

UPDATED: November 28, 2018


1) Install the new version of Vault on a new server. I'd recommend installing both the Vault server and also Serviceweb2, which you can use for testing the new install

2) Copy INI files from the old server to the new server (check to make sure that you don't have paths or IP addresses in the INI files that could cause conflicts where two versions of Vault try to write to the same set of files!) including profiles.ini / database.ini / server.ini / e2serverd.ini / e2renderd.ini(s) / e2routerd.ini.

3) Copy the contents for the following folders on the old server to the new server:

a) server/index/    (note that if you are migrating FROM a version of Vault older than 6.x, you are advised to rebuild the indexes instead of copying them)

b) server/docdata/

c) server/pagedata

d) server/distrib/<resourcesetname>

e) server/distrib/default (only if you had configured the old server to write files there, otherwise you don't need to copy these files)

f) render/distrib/<resourcesetname> (for each render)

g) render/default (for each render, but only if you had configured the old server to write files there, otherwise you don't need to copy these files)

4) Start Vault services and test by trying to view files using a Vault client. If you are using custom clients / APIs you will also want to test those methods thoroughly as there could be some changes between the old version and the new version.

Environment Details

Vault on Windows, 6.x and higher

Downloads

  • No Downloads