Skip to content

How to Migrate Elliott to a New Server

Release Date: 05/23/2024
Version: 7.x & Up

Q - I am looking for steps to move Elliott 8.5/PSQL 11 on Windows Server 2012 VM to Elliott 8.5/PSQL 15 on Windows Server 2022 VM. 

A - In short, you can take the following steps:
(1) To install PSQL on the new server, pleaser see this KB article:
If you already installed PSQL on the new server, pay attention to the video at the end that discusses the subjects of (1) Release file size 2GB limitation, and (2) NTFS security. Make sure you do not miss these two steps.

(2) To migrate Elliott, you should create a share on the new server same as your older server's Elliott share name. Make sure there's no one with open files on your old server's Elliott share.  You can find this out by using the PSQL monitor on your old server to see who has open Elliott files and get those users to log out. Then you can copy the entire Elliott folder from the older server share to the new server share. To test, you can map one of your workstation's Elliott drives to the new server's Elliott share by using the same drive letter.  After re-mapping the Elliott drive to the new server, you should be able to start testing with the new server.

(3) On the new server, you can optionally upgrade to new Elliott version by using the following KB article:

(4) To switch to the new server, re-copy all *.DAT and *.BTR files in the <ElliottRoot> and <ElliottRoot>\DATA* folders. Make sure no users have open these files when you copy.  After that, re-map all your users' Elliott drives to the new server. This can be done either manually or automatically by running a script though group policy.  If you also upgrade the Elliott version, you should create the desktop  shortcut of Elliott 8.5 or 8.6 on users' workstations as in the previous KB article.

(5)  If you implemented NTFS security on the older server, you can reference the following article on how to apply NTFS security on the new server's Elliott share:


EMK

Feedback and Knowledge Base