Upgrades and Reinstalls of FRP
|
8/29/2010 9:19 AM |
|
Problem:
1. I want to upgrade my FRP to a new release. What are the procedures?2. I have a lot of off-site servers that I need to upgrade, is there a way to do this with a script?
3. I Need to reinstall FRP - Follow the Major Upgrade instructions, use the same version installer as on all other machines. Do not mix versions of FRP!
NOTE: A current support contract is required for all servers in your group to Upgrade FRP. If your support is expired you can renew Here.
Solution:
There are several ways to upgrade FRP depending on what version you currently are running.NOTICE: If you are upgrading and skipping more than a couple of versions IE: 5.x to 6.x you will not be able to preserve your Jobs and settings. In this case you will need to follow the steps below for Upgrade skipping versions. If you are upgrading from a version close to the current version IE: 6.2 to 6.3.X you can use the Major Upgrade instructions.
If your version is in the 5.X series or older you will have to do a complete removal of FRP from all machines and install fresh with the new version and recreate all your servers and jobs as provide below Upgrade - skipping versions.
Note: There are different commands to stop and start on the MAC noted near the end of this article.
Upgrade - skipping versions IE: 5.X to 6.X versions
We recommend you make screenshots of your server and job list to aid in recreating them after installing.
1. Stop all FRP services on all servers
2. Wait 5 minutes.
3. Completely delete the /FileReplicationPro install folder on all servers
4. Install the Management and Replicaiton server on your ONE management machine.
5. Install the same exact version of FRP Replication only service on all other machines.
6. Rebuild your server list and jobs.
Major Upgrade - Use in most cases or if there is any doubt
On the (one and only) Management Server in your group:
1. Stop all FRP services.
2. Make a backup of the following files:
Backup The /FileReplicationPro/etc/ folder with all of it's contents.
The following refers to installations with customized memory settings usually systems replicating over 1TB of data and or 500,000 files or more.
**Backup the Java Heap settings if you have increased the memory for FRP Replication. Since the FRPRep.lax, FRPRep.ncf, or Info.plist file associated with the FRPRep.app may have changed between versions you will need to check what the current setting is that you made and make a note of the modified value the repeat the process on the upgraded install to restore your preferred memory setting. See http://fb.filereplicationpro.com/default.asp?W72
3. Un-install FRP
4. Delete the /FileReplicationPro installation folder
5. Check to be certain no FRP.... services are running on the machine, even if you indicated no in the installer. Install FRP
6. Replace the backed up /etc folder over writing what is already there. Place your backed up s2s.properties file from version 6.0 or earlier into the /etc folder.
7. Start FRP services in this order: FRPRep, FRPHelp, FRPMgmt (The last 2 services are started only on a management server) See ** NOTES for Other OSes below
On all other servers in your FRP group (no matter how many)
1. Stop all FRP services, wait 5 minutes.
2. Make a backup of the following files:
Backup The /FileReplicationPro/etc/ folder with all of it's contents.
The following refers to installations with customized memory settings usually systems replicating over 1TB of data and or 500,000 files or more.
**Backup the Java Heap settings if you have increased the memory for FRP Replication. Since the FRPRep.lax, FRPRep.ncf, or Info.plist file associated with the FRPRep.app may have changed between versions you will need to check what the current setting is that you made and make a note of the modified value the repeat the process on the upgraded install to restore your preferred memory setting. See http://fb.filereplicationpro.com/default.asp?W72 If you have many replication only servers you can modify one server's file and and then copy it to all the others. Restart FRPRep on each server to take effect.
3. Un-install FRP
4. Delete the /FileReplicationPro installation folder
5. Check to be certain no FRP.... services are running on the machine, even if you indicated no in the installer. Install FRP
6. Replace the backed up /etc folder over writing what is already there. Place your backed up s2s.properties file from version 6.0 or earlier into the /etc folder.
7. Start ONLY the FRPRep service. It is best if you disable the other two FRP services. See ** NOTES for Other OSes below
Minor Upgrade (The release must be noted as a minor upgrade to use this process, if you have any doubt, use the Major Upgrade process.)
On all servers:
1. Stop all FRP services, wait 5 minutes.
2. Use the Un-installer to remove FRP (Do not apply the upgrade over the old version without this step.)
(To maintain existing jobs and licenses - Do not delete the FRP home folder)
3. Install the new version
4. Start FRP services on the management server in the following order FRPRep, FRPHelper, FRPConfigMgmt. See ** NOTES for Other OSes below
5. Start FRPRep service only on all other servers. See ** NOTES for Other OSes below
Patch fix (rarely performed)
On all servers:
1. Stop all FRP services, wait 5 minutes. See ** NOTES for Other OSes below
2. Copy any patch items to their respective directory (usually diasoft.jar and diasoft.war into \FileReplicationPro\lib )
3. Start FRP services on the management server in the following order FRPRep, FRPHelper, FRPConfigMgmt
4. Start FRPRep service only on all other servers.
2. Offsite Server Upgrades
Version 6.2 or Later ONLY
This procedure is described for replication only servers which is the situation 99% of the time with offsite servers.
Be very careful to remember that only ONE server in your replication group (whether 2 or 100 servers) can run the Management and Helper services.
You may want to use a script to download the latest FRP version to each machine in your network. Of course it is possible to use FRP to distribute the upgrade files and scripts to your remotes (into a "side directory") and then execute the scripts. This requires creating a replication job for each server. Alternatively you can write custom scripts which will read from a list of remote servers and repeat the process for each one in turn.
Here is an example for Windows which has been used. The console install command line is:
<path>frpro.exe -i console
Use a script to stop all FRP... services on the remote server.
Pause 5 minutes.
Use the script to backup the <path>\FileReplicationPro\etc\ folder with all of it's contents
Delete the entire /FileReplicationPro/ folder structure prior to the install.
Execute the correct command line to install on your OS
Once the install is completed you should have a script run to stop all FRP... services once again to prevent any unwanted services running.
Restore the previously backed up \FileReplicationPro\etc\ folder with all of it's contents.
Then execute a start of the FRPRep service.
** NOTES for Other OSes
For Mac
FRP.... Services should be stopped using the Force Quit command in Activity Monitor
The only reliable manual way to start FRP..... services in a terminal window with systemstarter commands in the following order:
sudo SystemStarter start FRPRep
sudo SystemStarter start FRPHelp
sudo SystemStarter start FRPMgmt
UNIX/Linux run:
$ chmod 777 frpro.bin
$ ./frpro.bin -i console
or
$ ./frpro.bin -i silent
It is possible to install FRP from the command line with the command line, you will need to experiment a bit with OSes other than windows to work out he best approach that gives the result you need.