Best Practice / Experiences: in Place migration SP (Distributed Architecture) from an existing Domain into a new Domain under running Production (Pharmaceutical companies

Hi,

Please see below,

there are two ways of doing this, both are similar but the first one has lower risk than the second one.

First method:

1) Take a backup of the current system

2) Create new VMs of your current setup and install the Aveva softwares with the new Active Directory connected

3) Deploy and have both the old and new running , and then you can deprecate the current system by undeploying the old Galaxy and removing it from the old Active Directory 

Second Method:

1) Take backup of the Galaxy 

2) Force all your app engines and OI server to secondary AOS

3) Undeploy ONLY your primary AOS

4) Create 1 new GR Node with new Active Directory connected and move the AOS1 to the new Active Directory

5) Since the AOS1 cannot see the historian at this point , it will go in store forward mode, make sure before you deploy store and forward settings in AOS1 is setup correctly

6) Undeploy Historian from old Active Directory and deploy in the new Galaxy and active directory

7) Lastly move AOS 2 to the new Galaxy and Active Directory

If you’re in a pharma company I would prefer the first option.

Warm Regards,

Rainer

My recommendation is the first option that Rainer suggests. Typically, when doing this process in a pharmaceutical environment, it is necessary to validate part of the new installation and that usually takes a few days. Having the 2 environments in parallel allows you to verify that everything works well and in order not to lose the alarms and history, what you can do is copy the HBs of the last few days from the "old" environment to the new one and in this way there is no loss of information.