Keyword search: 

Enhanced Migration Support

12/14/2011 5:18 PM
You can subscribe to this wiki article using an RSS feed reader.


For customer with less than 20 servers see upgrading versions of FRP


Enhanced Migration Support for large customers. Due to the needs of our larger customers (e.g. 20+ servers), we have enhanced the migration tools so FRP can now support migration from any older versions of FRP prior to version 6.3.0 to the latest. Previously when a number of versions were missed, it was not possible to upgrade and preserve the server list and jobs.  We can now offer assistance with this process for those who need it.  Contact support for details and a quote.

This is a very touchy proceedure for which we have written special inhouse tools to convert the configurations to a newer version,  it requires a number of steps on the part of the customer as well as FRP developers and support staff.   We have summarized the steps below, but the tools needed for this process will remain in our labs since the process requires close supervison and quality checking before placing it into production on a customer site.



OVERVIEW of the Process

    Migration support: To migrate from any older version prior to 6.3.0 to the latest  version of FRP, the core code for the configurations must be modified. Our support is also required to make any migration sucessful in this type of situation.
  
Here are the migrations steps the customer needs to follow:     
     
1) A utility we supply to generate the file .frp_id needs to run on the all the Systems. The new file .frp_id will have the unique computer id.
          
2) The user the needs to provide a mapping file according to the specifications we provide which contains key value pair where key is the hostname and value is the content of the .frp_id to us.
              
            eg: samambha=-79e965d2:130f38563c0:-8000
           
3) Upon reciept of  the mapping file and older configuration file from the customer we generate the latest FRP configuration file in our lab. 
    
4) The customer systems are still running the older version of the FRP during the above steps.

5)  After creating the new configuration, reviewing and testing it we send the new configuration to the customer.
        
6) Once the customer reviews / tests the configuration and is fine with the new configuration in his lab, he can start updgrade all the systems to latest FRP.
        
7) Upgrade process, Stop the FRP.... services on all servers after 10 minutes, remove all files and folders in the /FileReplicationPro  folder.  Run the new installer making all machines replication only machines except for the one and only Replicaiton and Management server.   Replace / insert  the .frp_id file  in the \FileReplicationPro\etc  folder with the  .frp_id file  (Generated in Step 1). Ensure the right frp_id file is placed on the correct machine as it came from in step 1.  The configuration .xml file is also replaced in this folder on all machines with the new generated version.
        
8) Restart the FRPRep services on all servers.   On the one and only Management and Replication server also start FRPHelp and FRPMgmt services.  Login to the GUI on that server at it's IP address on port 9100.  IE:  http://10.0.0.1:9100

Tags:
Home: WIKI - Knowledge Base Index What's new: Recently changed articles