NOTE: To Upgrade or Reinstall a current support contract is required for all servers in your group. Upgrading without a current contract will result in a non functioning installation. If your support is expired you can renew Here.
From Version 6.5.0 All Windows OSes Require .NET 3.5 or higher and Microsoft C++ redistributable
There are several ways to upgrade FRP depending on what version you currently are running. Be aware that ANY reinstall or upgrade will require current support contract on all of your servers and new license keys. Failure to have coverage and obtain new license keys will render your installation invalid and it will not function.
NOTICE: If you are upgrading and skipping more than a couple of versions IE: 4.x or 5.x to 6.2.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 When skipping versions in section 2 below. If you are upgrading from a version close to the current version IE: 6.3.X to 6.5.4 but not greater than 7.0 you can use the Major Upgrade instructions in section 1 below.
If you are upgrading from version 7.0 to a newer version such as 7.5 or later, you can just run the 7.5 installer over your old installation to upgrade. This does not work with versions <7.5 and will break your installation. For older installations use the appropriate instructions found elsewhere on this page.
Never mix FRP versions in an installation, corruption of the entire installation may result. The version of each of your servers can be seen in the server list of the GUI, each server is listed on a line by hostname the FRP version appears in the items to the right of the server hostname. If you have a doubt about upgrading between versions contact support@filereplicationpro.com and inquire stating what your current installed version is.
Note: There are different commands to stop and start on the MAC and other OSes noted near the end of this article.
Reinstall or upgrade of version 7.0 or later.
If you are upgrading from version 7.0 to a newer version such as 7.5 or later, you can just run the 7.5 installer over your old installation to upgrade. This does not work with versions <7.5 and will break your installation. For older installations use the appropriate instructions found elsewhere on this page.
1. Versions =>6.3.0 =<7.0
---- Preparation Steps ----
Download the correct package (32 or 64 bit) for your OS with VM unless your are on a MAC which has it's own VM. OSX runs it's own 64 bit VM on some versions of OSX for which you will want to use the NoVM version. For versions of OSX without a VM download the VM version.
Install or to upgrade to .NET version 3.5 or higher on Windows machines.
For a reinstall be certain to install the exact same version of FRP as already on the machine, installing a different version, mixing versions in the same group will cause you many problems. In a re-install pay careful attention to the role of your server that is to be reinstalled, and use the correct section below for Replication only servers or the one and only Management server.
For an upgrade you will need to plan to move all servers to the same version of FRP at the same time. Attempting to run FRP with different versions can result in either unpredictable results or corruption of your configuration files.
MAC users see **NOTE below near the end of this page before proceeding.
From Version 6.5.0 forward, All Windows Versions Require .NET 3.5 or higher, you must provide this yourself.
Versions of FRP for Windows also require Microsoft C++ redistributable which is provided in the installer.
OSX Yosemite virtual and headless machines will require installation using the terminal based non - GUI method.
Step by step instructions for upgrading version 6.3.0 and later to Version 6.5.0 These instructions will preserve your server list, settings, license keys and jobs.
Critical to Success:
Run the FRP un-installer found in the /FileReplicationPro install folder or on some versions in /FileReplicationPro/uninstaller
This will remove everything but the license, server configuration and jobs configurations. This provides a means for you to upgrade and preserve all of your settings except for customized memory settings which you will need to re-do after your upgrade.
---- Management Server ---
On the one and only management server backup the /FileReplicationPro/etc/ folder.
You should name the backup by it's hostname to prevent any confusion in the future. If you should loose your configuration, license, and jobs you can restore it by placing the backed up files in the /etc folder. TIP: These are the files which should be regularly backed up if you wish to protect your self from loss of the jobs and settings due to a system crash or other event.
See note below if upgrading from 32 bit to 64 bit FRP.
If you have not already done so, login to the server under an account that has full domain rights to all the files and folders which will be replicated from or to any other machine in the system. This is critical for the replication of ACLs, NTFS permissions etc. Failure to do this step correctly will result in non replication of ACLs, the warning "ACL ERROR 1307" in logs or even inability to replicate some files and folders.
Run the installer on your management server, accept the license agreement and default path. If you are asked to, allow files to be overwritten. Use the option to install the Management and Replication option.
On OSX Yosemite and some other OSX virtual and headless machines the installer will not run in GUI mode due to a known OSX bug that Apple must resolve. You can install from the terminal using the command ./path/to/installer.app/Contents/MacOS/installbuilder.sh --mode text Do not permit the installer to start FRP but finish the installer then REBOOT the OSX server
On Windows permit the services to be started at reboot when asked by the installer. If on another OS it is wise to create a starutp script to start the FRPRep, FRPHelp and FRPMgmt services on reboots.
On OSX machines only after installing version 7 or later of FRP you must reboot the machine, you will not be prompted to reboot. But it's necessary that you do so.
You may allow the service to start if on windows, Linux requires that you launch the services from the terminal.
Login to the management console. Note: the default login is "admin" password is "admin" or use a previous account you created.
IMPORTANT:set the IP address of the management server in the menu from the upper right of the GUI systems/system settings. (Details)
* Upgrading to 64 bit from 32 bit. After backing up the /etc folder and having waited at least 10 minutes after stopping the FRP services, Run the installer for the 64 bit program using the same steps as used to install the 32 bit program. The file location is for 32 bit is C:\Program Files (x86)\FileReplicationPro and the new 64 bit one is C:\Program Files\FileReplicationPro. After doing the install for the 64 bit program check the services to insure that it did not start, it if did, stop it and wait a few minutes before proceeding. Copy your back up of /etc to the new location.
Then you may restart the services. Do not fail to completely delete all the files and folders in the C:\Program Files (x86)\FileReplicationPro folder.
--- For all Remaining Servers in your group -----
These steps will need to be performed on each of the remaining replication machines .
Backup the /FileReplicationPro/etc/ folder on each machine.
You should name the backup by it's hostname to prevent any confusion in the future. If you should loose your configuration, license, and jobs you can restore it by placing the backed up files in the /etc folder. TIP: These are the files which should be regularly backed up if you wish to protect your self from loss of the jobs and settings due to a system crash or other event.
If you have not already done so, login to the server under an account that has full domain rights to all the files and folders which will be replicated from or to any other machine in the system. This is critical for the replication of ACLs, NTFS permissions etc. Failure to do this step correctly will result in non replication of ACLs, the warning "ACL ERROR 1307" in logs or even inability to replicate some files and folders.
On OSX Yosemite and some other OSX virtual and headless machines the installer will not run in GUI mode due to a known OSX bug that Apple must resolve. You can install from the terminal using the command ./path/to/installer.app/Contents/MacOS/installbuilder.sh --mode text
Run the installer on your server, accept the license agreement and default path. If you are asked to, allow files to be overwritten. Use the option to install the Replication ONLY option.
On OSX Yosemite and some other OSX virtual and headless machines the installer will not run in GUI mode due to a known OSX bug that Apple must resolve. You can install from the terminal using the command ./path/to/installer.app/Contents/MacOS/installbuilder.sh --mode text Do not permit the installer to start FRP but finish the installer then REBOOT the OSX server
On Windows permit the services to be started at reboot when asked by the installer. If on another OS it is wise to create a starutp script to start the FRPRep, FRPHelp and FRPMgmt services on reboots.
Repeat the above steps on all remaining replication machines.
* Upgrading to 64 bit from 32 bit. After backing up the /etc folder and having waited at least 10 minutes after stopping the FRP services, Run the installer for the 64 bit program using the same steps as used to install the 32 bit program. The file location is for 32 bit is C:\Program Files (x86)\FileReplicationPro and the new 64 bit one is C:\Program Files\FileReplicationPro. After doing the install for the 64 bit program check the services to insure that it did not start, it if did, stop it and wait a few minutes before proceeding. Copy your back up of /etc to the new location.
Then you may restart the services. Do not fail to completely delete all the files and folders in the C:\Program Files (x86)\FileReplicationPro folder.
------
Return to your Management GUI and login, With this version (since 6.4.6) you will notice that a login name is now required, the default is admin and the password is admin. If you already were on version 6.4.6 prior to this upgrade your user accounts will be unchanged.
Your servers should either already be online or come online shortly. If they do not make sure the Management Server external IP address has been entered into your console from the Settings / System Settings menu item in the upper right of the GUI window. Also double check to see the FRPRep service and only that FRP... service is running on each of the replication only servers.
Your previously existing jobs will be in the jobs window, each job should initialize (may take from seconds to many minutes if they are large) then kick off a replication to check for changes.
------- End of Major Upgrade instructions ---------------------------
2 Versions =<6.3.0 you must use this method to upgrade to newer versions
We recommend you make screenshots of your server and job list to aid in recreating them after installing.
---- Preparation Steps ----Download the correct package (32 or 64 bit) for your OS with VM unless your are on a MAC which has it's own VM. The MAC runs it's own 64 bit VM.
Install or to upgrade to .NET version 3.5 or higher on Windows machines.
1. Stop all FRP services on all servers (FRPRep, FRPHelp, FRPMgmt)
2. Wait 5 minutes.
3. Completely delete the /FileReplicationPro install folder on all servers
4. Install the Management and Replication server on your ONE management machine. If you OS type Linux, Novell, Unix requires it start the FRPRep FRPHelp and FRPMgmt services (in order) from the installer folder with an account that has rights to all the files and folders in any jobs.
5. Install the same exact version of FRP Replication only service on all other machines. If you OS type Linux, Novell, Unix requires it start the FRPRep service from the installer folder with an account that has rights to all the files and folders in any jobs.
6. If upgrading to version 6.4.6 from an earlier version you will now have the ability to have multiple logins and accounts with different rights. Your Admin password will be "admin" the user name for the admin account will be "admin" You should change these after logging in.
7. In the upper right corner of the GUI click on Settings then System Settings find the fox labeled "Management Server External Address(es)*" enter the one static IP address that all of your servers will be able to use to contact your management server.
8. Rebuild your server list and jobs.
------- End of Upgrade when skipping several versions ----------
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.
3. 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.
Use a script to stop all FRP... services on the remote server.
Pause 5 minutes.
Use the script to backup the following files in \FileReplicationPro\etc\
Delete the entire /FileReplicationPro/ folder structure prior to the install.
Execute the correct command line to install on your OS The console install command line is: <path>frpro.exe -i console
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:
Versions prior to Yosemite
sudo SystemStarter start FRPRep
sudo SystemStarter start FRPHelp
sudo SystemStarter start FRPMgmt
Yosemite and later versions
open FRPRep.app
open StopFileReplicationPro.app
Command Line Install Syntax
./path/to/frpro.app/Contents/MacOS/installbuilder.sh --mode text
UNIX/Linux GUI Install:
$ chmod 777 frpro.bin or frpro.run as the case may be
$ ./frpro.bin -i console or frpro.run
Or for a command line install
$ ./frpro.bin -i silent
$ ./frpro.run --unattended