Forum Discussion

YoungWaiter's avatar
YoungWaiter
Ideator I
3 months ago

How to Migrate the Aras Innovator Environment to a New Server

I am a beginner who has been using Aras for only a few weeks.

I would like to replace the server machine that currently hosts Aras.

Assuming the drive configuration remains the same, I want to migrate the entire existing Aras environment (Innovator Server, SQL Server, and Vault Server) to the new machine.

For SQL Server, I believe I can export the database to a .BAK file, install SQL Server on the new server machine, and restore the .BAK file there.

For the Vault Server, I believe I can simply copy and paste the entire folder that serves as the Vault storage.

However, I do not know how to migrate the custom configuration portion of the Innovator Server.

How can I move the environment so that the post-replacement system is the same as before the replacement?

-----------Jananese----------

私はArasを初めて数週間のビギナーです。

現在、Arasの入っているサーバーマシンをリプレイスしたいです。

ドライブ構成は同じとして今のAras環境（Innovatorサーバー、SQLサーバー、Vaultサーバー）すべてを持ち越したいです。

SQLサーバーはデータベースを.BAKファイルに書き出し新しいサーバーマシン内にSQLサーバーをインストールした上で.BAKファイルをレストアすれば良いと思っています。

VaultサーバーはVaultストレージとなっているフォルダを全てコピー＆ペーストすれば良いと思っています。Innovatorサーバーのカスタム設定部分の持ち越し方が分かりません。

どうすれば環境をリプレイス前と同じ環境をリプレイス後に移動することができますか。

 

Inventor

2 Replies

  • angela's avatar
    angela
    Catalyst II
    3 months ago

    This is what I did in the past:

    1. Use a tool like "Beyond compare" to compare your new Innovator installation with the previous version. This way you can discover differences in the code tree. Document all of the differences and merge them to your new server. Some of the official Aras upgrade patches might look not important, but they often are. It´s a huge benefit so have an overview of custom patches, so really document them! In my case I have simply list of all changed files and what´s the pupose of a specific patch.

    2. Link existing data base to new server if db server stays the same. Or use the bak file if you have a new database server.

    3. I just copied&pasted the previous Vault files to new file Vault. But pay attention! The folder permissions for existing files are destroyed which can lead to an hidden error: There is a change that deleted files aren´t deleted anymore:

    "Multiple Errors: DoPhysicalFiles - Access to the path is denied. " when deleting files. What permission shall I use? | Aras

    Solution: Restore the folder permissions with PowerShell. I expect there is a more professional solution available than Copy&paste, but this is what I did back then. 

     

  • MaksymArchybasov's avatar
    MaksymArchybasov
    Creator II
    2 months ago

    the way I did it: 

    1. Get SQL Backup on main SQL Server  and restore  it on the new Server
    2. Get the installation kit for your Aras Innovator version from Aras FTP 
    3. Copy Vault Storage ( try to keep the same path . e.g. "D:\Vault\myInnovator")
    4. Install the Aras Innovator on the new server. Note - try to keep the same installation Path if possible ( you'll have a less modification in config files ). Also if possible to repeat the same password for certifactes" which has been used in original installation (usually you can find in in Oauth.{ModuleName}.config file). 
    5. When installing Aras, at the step of  DB server configuration - choose "existing DB" which is newly restored DB. 
    6. At this point  you should be able connect to your server at least as "admin" account on localhost. 
    7. Copy Code Tree ( the full folder from your previous location)  - preferably use 7zip 
    8. Unzip Code Tree  on temp location of the new server. Go to every folder and delete the folders named "App_Data" which will be present for every module (even in the Innovator\Client and Innovator\Server) . This is where security  certificates are stored, and it will be created  on standard installation. 
    9. After the cleanup - Copy with replacement the code tree to the new location. 
    10. Check all the config files on having obsolete paths. restart IIS 
    11. Test :) 

    Basically that's it.. It takes like 2 hours usually.

    But again - it's only when you need to move the same solution from one server to another. If it comes to the version upgrade, things are a bit more complicated.