(1) Prerequisites:-
Original architecture: Already installed
1) PrimaryDirector_1 
2) SecondaryDirector_1
3) Broker
4) Engines 
5) DriverSDK

Current Working:
a) Brokers connect to PrimaryDirector_1 
b) Engines connect to PrimaryDirector_1 
c) Gridflooder runs without issues
--------------------------------------------------------------------------------------------------------------------------------------------------
Steps: 
(2) PrimaryDirector_1 is shut down (Testing current SecondaryDirector_1 acting as Primary Director)
a) Brokers connect to SecondaryDirector_1
b) Engines connect to SecondaryDirector_1
c) Gridflooder runs on SecondaryDirector_1

(3) Setting up new SecondaryDirector_2 
The original SecondaryDirector_1 was shut down and a New SecondaryDirector_2 was installed, this New SecondaryDirector_2 points to Original PrimaryDirector_1, and once the New SecondaryDirector_2 is active, the following needs to be reconfigured
a) Director: Nothing to reconfigure but was verified that C:\datasynapse\gs700HF10\manager-data\deploy\resources\gridlib, gridflooder library is not present on the second director
b) Broker: Reinstalled and pointed to the New SecondaryDirector_2
c) Engine: Change the configuration of the engine to point New SecondaryDirector_2, after that all the engines are restarted Engine configuration is copied on the secondary Director but not the service types (.gsdd)
d) Driver SDK requires editing the driver.properties to point to the New SecondaryDirector_2 and works fine.

(4) Reconfiguring current PrimaryDirector_1 after Installing new SecondaryDirector_2
a) Director PrimaryDirector_1: Reinstall the manager and configure the PrimaryDirector_1 to recognize the new
SecondaryDirector_2
1) Enter the Secondary Director’s address and port on the corresponding page.

(5) Promoting new SecondaryDirector_2 to New PrimaryDirector_2
b) Shutdown the PrimaryDirector_2 and Promote the SecondaryDirector_2 to become the PrimaryDirector_2
c) Reconfigure the components (Secondary Director is not present until reconfigure to New PrimaryDirector_2)
d) Director: Reinstall the director and change the following parameters to make it PrimaryDirector_2

1. Type: Primary

e) Broker appears on newly promoted PrimaryDirector_2 but broker should be reconfigured so that it will have the new Primary Director URL.
f) Engine configuration, the configuration used by engines was successfully transferred or exist in the new PrimaryDirector_2 
g) Driver: driver.properties file should have new Primary Director and Secondary Director URL to sync new gridlibs which are required to run some examples in future.

Important points to note:
1) The Gridflooder library does not appear in the UI of new PrimaryDirector_2
2) Also, it does not appear in the SecondaryDirector_2 before it was promoted to PrimaryDirector_2
3) But the driver was able to run successfully
4) This is because the Gridflooder was already loaded on the engine side and also the broker side, that’s why the driver runs successfully even if not appearing in the UI
5) Sync grid libraries from old Primary Director to new Primary Director (manually copy)
 

Steps to migrate existing Gridserver environment from one Machine to another machine

Windows

PFA a pdf file which contains a demonstration of the migration test done for similar case