Sometimes there is a need to move the management server and the administrator would like to preserve all the job settings rather than recreate them. This method will permit such a move and minimize the work involved.
If you move the hardware to a new site with FRP already installed, and the IP address changes you can ignore the section in the directions below that refers to copying the program files for FRP over to the new hardware. Proceed with the steps to edit the configuration.xml file on the management server and the steps following that.
These instructions apply only to moving your one and ONLY Management server, use the instructions for moving a replication server for your other servers.
BEFORE PROCEEDING:
Go to your old Management server and disable the service.msc entries for FRP Management, and FRP Help. If on and OS other than windows go to your system startup script folders and disable or edit the scripts that start the Management and Helper services.
Stop FRP on all servers, THEN wait 3 minutes.
You must install the same version of FRP on the new server using the installer prior to doing the next steps. After installing FRP on the new server check it's services and be certain the following services ARE NOT running. If these services are running stop them before proceeding.
FRPRep
FRPHelp
FRPMgmt
Delete the /FileReplicationPro/etc/configuration.xml file on all servers EXCEPT the management server copy of configuration.xml.
Next you will modify the configuration.xml file using a plain text editor (not xml editor) to contain the new IP and host name, the group name will also change to reflect the new host, so you may need to change the group name all the way thru the file under the tag ComputerID
Open the configuration.xml file look at the top for the following tag sets. In this example the Management console is installed on hostname NewYork and the LanID is NEWYORK.
Next you will search and replace every occurance of the computer's hostname (NewYork) reguardless of case, upper or lower case is not critical.
Search and replace EVERY occurance of your host name that occurs in the file until the end with the new hostname of your management server.
Some examples of the tags which will contain the host name, there may be other tags than these shown, replace the hostname everywhere it occurs in the file.
<LanMaster><LanID>NEWYORK</LanID>
<ConsoleHostName>NewYork</ConsoleHostName>
<ComputerMaster><LanID>NEWYORK</LanID>
<HostName>NEWYORK</HostName>
Next you will search for and replace the old Internal and External IP address(s) of your management server in the configuration.xml file wherever it occurs. You may find the management server IP address in tags with different names, replace each of the IPs whever it occurs and as many times as it occurs.
Examples are
<IPAddress>10.0.0.2</IPAddress> This is one of the internal IP addresses to search and replace, there may be serveral more you will need to search and replace for. IF the old server had more IP addresses IE: 10 IP addresses and the new server will only have 5 internal IPs, search for each of the extra old IPs and replace them with 0.0.0.0 all the way through the file.
<MgmtExternalAddress>1XX.218.62.169</MgmtExternalAddress> This is the IP address that all servers can reach your Management server at via the Internet when they are offsite. IF the old server had more external IP addresses than one, search for them and replace them with 0.0.0.0 all the way through the file. The intention is to leave only ONE valid external IP addressfor the new server.
Look for the Sequence taq near the top of the tile <Sequence>224</Sequence> Whatever the number is for the sequence increase it by 10.
Save the file.
Copy the contents of the /FileReplicationPro/etc folder to the same location on the new management machine.
The destination path for any jobs that the old server was running must be created on the new machine. Copy any data for those folders to the new machine.
Make sure the old server is not running any of the old services.
Restart the management server first in the order FRPRep, FRPhelp, FRPMgmt.
Verify the settings in the GUI that the management server has the correct IP address and host name.
If all looks ok then bring up the other servers, the will each take a copy of the new configuration file from the management server as they come on line.
Also see the subject of More than One Management Servers