|
Moving a complete installation of Robo-FTP from one computer to another may be simple or complicated depending on your usage profile. You may find the following list helpful whether you are replacing your server, moving from a testing environment into production, or simply writing a disaster recovery plan.
Important
The instructions on this page are only applicable to the process of moving the current version of Robo-FTP to another computer running the same version of Robo-FTP. If you need to both upgrade to the current version and move to a new computer, you should first upgrade the old computer by following the upgrade instructions in the Migration Guide document distributed with the current version. Once you confirm everything is working in the current version on the old machine, follow the instructions on this page to move your Robo-FTP installation to the new computer.
| 1) | Copy the entire Robo-FTP installation directory (including sub-folders) from the old machine to the new machine and, if at all possible, keep the installation folder path exactly the same. Although this step is not strictly necessary, it makes the process of moving an installation significantly easier and also reduces the chances for error. If your Robo-FTP installation on the old machine is configured for multiple users you should also copy the \My Documents\Robo-FTP X.X and the \Application Data\Robo-FTP X.X folders for each user to their corresponding folders on the new computer. The precise location of these folders will vary by your version of Windows. |
| 2) | Install Robo-FTP on the new machine. If you copied the installation folder from the old machine then install Robo-FTP into the same folder. |
Note: Robo-FTP is 32-bit software so if you are installing it on a 64-bit version of Windows you won't be able to install Robo-FTP in a sub-folder under \Program Files. If you click the "Custom" button during installation and choose the \Program Files folder then Windows will automatically force Robo-FTP to be installed into the \Program Files (x86) folder instead. If you are moving from 32-bit Windows to 64-bit Windows you may need to change where you copied the folder in step 1 above.
| 3) | If you are moving from a 32-bit version of Windows to a 64-bit version, you won't be able to install |
| 4) | Export settings from the old machine and import them on the new one using the "Export Settings" and "Import Settings" options from the File Menu on the main console window. If your Robo-FTP installation on the old machine was configured with shared settings you only need to import one settings file on the new computer. If instead your Robo-FTP installation on the old computer had settings defined on a per-user basis, you'll need to have each user individually export settings from the old computer and import settings on the new computer. |
| 5) | Find all the command script files that you use on the old computer and move them to the new one. If you did not install Robo-FTP to the exact same folder on the new computer as it was on the old computer then you'll need to review each of your command scripts and update any that reference the old path. |
| 6) | Make sure that any files or folders referenced in your command scripts also exist on the new computer. If you copied the entire installation directory from the old computer then chances are good that many of these files were already copied. For example: |
| a) | If any of your scripts use the CRON command look for event file(s). The default filename is crontab.txt. |
| b) | If your scripts use the set of commands for finding differences (DIFF, GETDIFF, FTPDIFF, and FTPGETDIFF), then look for the related snapshot databases. The default names of these files are snapshot_local.sql and snapshot_site.sql. |
| c) | Find and transfer any other files or folders referenced in your command scripts. |
| 7) | Export PGP Keys from the old computer and Import them on the new one. Any keys installed in shared mode on the old computer will already be on the new computer if you copied the Robo-FTP installation directory as suggested in Step #1. |
| 8) | If you connect to any secure sites, transfer the associated SSL and SSH certificates and keys. |
| a) | Robo-FTP tracks trusted FTPS and SFTP sites with a pair of sub-folders named "Trusted Certificates" and "Known SSH Sites" which, if you copied the entire installation directory from the old computer, will already be populated on the new computer. Alternatively you can reestablish the trust relationship with secure sites by connecting with the FTPLOGON /trust=all option. |
| b) | Connecting to some secure sites requires more than a simple username and password. If you use Robo-FTP to connect to FTPS or HTTPS sites that require SSL client certificates or SFTP sites that require SSH client keys then these files must be transferred to the new computer. If you generated your client certificates or keys using Robo-FTP then the files are most likely in the installation folder on the old computer because the Configurator creates them there by default. If you are having difficulty locating all of your client certificates and keys, try using a text editor to examine the settings file(s) exported from old computer. |
| 10) | If any of your scripts include the DBUSE command with the /odbc option you'll need to recreate the associated ODBC DSN on the new computer. |
| 11) | If you use Windows Scheduled Tasks or batch files to launch Robo-FTP these will need to be copied to the new computer. |
| 12) | Test to be certain everything is working to your satisfaction on the new machine and then transfer the license from the old machine to the new one. |
|