--- canonical: https://safekit.evidian.com/products/high-availability-software-for-application-clustering/safekit-release-notes-8-2/ SafeKit 8.2 Release Notes — Part 7 of 7 — Migration Instructions (section 4) --- # 4. Migration instructions ![*](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20266%20201'%3E%3C/svg%3E)![*](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image001.png)       [Section](#_Migrating_from_SafeKit) 4.1 “Migrating from SafeKit 7.4 or 7.5 to SafeKit 8.2” ![*](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20266%20201'%3E%3C/svg%3E)![*](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image001.png)       [Section](#_Migrating_from_SafeKit_16) 4.2 “Migrating from SafeKit 7.5.1 to SafeKit 7.5.2” ![*](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20266%20201'%3E%3C/svg%3E)![*](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image001.png)       [Section](#_Migrating_from_SafeKit_14) 4.3 “Migrating from SafeKit 7.4.0 to SafeKit 7.5.1”   This section gives instructions and recommendations for SafeKit server migration. ## 4.1      Migrating from SafeKit 7.4 or 7.5 to SafeKit 8.2 SafeKit 8.2 is not compatible with 7.5. Therefore, it is a major upgrade that requires to stop and upgrade nodes at the same time when migrating to release 8.2. This is a major upgrade detailed in [section](#_Major_upgrade) 1.2.2. Moreover, SafeKit 8.2 comes with a major change in internal data storage, web service and web console. You cannot apply the standard procedure but only the one described below. ### 4.1.1          Upgrade procedure SafeKit is installed in: | | | | | --- | --- | --- | | | Windows if %SYSTEMDRIVE%=C: | Linux | | SAFE | C:\safekit | /opt/safekit | | SAFEVAR | C:\safekit\var | /var/safekit | #### 4.1.1.1       Pre-upgrade operations On each node to migrate: 1.    Log as administrator/root 2.    For a mirror module Note the server in the ALONE or PRIM status to know which server holds the up-to-date replicated files 3.    Run the command safekit module listid to know the installed modules and note their ids This is necessary if you have more than one module installed and if the value of the communication ports used by the module is important in your environment. 4.    Create a backup folder for saving SafeKit configuration files ·         Copy the file SAFEVAR/cluster.xml into your backup folder ·         For each installed module, run the command safekit module package -m *AM* /*AM*.safe Replace *AM* by the module name ·         Copy the directories SAFE/web and SAFE/snmp into your backup folder. This copy is necessary only if you have changed the default settings 5.    Optionally, take snapshots of modules Uninstalling/reinstalling will reset SafeKit logs and dumps of each module. If you want to keep this information (logs and last 3 dumps and configurations), run the command for each module safekit snapshot –m *AM* /snapshot\_xx.zip Replace *AM* by the module name #### 4.1.1.2       Old SafeKit package uninstall On each node to migrate: 1.    Log as administrator/root 2.    Open a PowerShell/shell console 3.    Stop all modules using the command safekit shutdown For a mirror in the PRIM-SECOND status, stop first the SECOND server to avoid an unnecessary failover 4.    Close all editors, file explorers, shells, or terminal under SAFE and SAFEVAR (to avoid package uninstallation error) 5.    Uninstall the SafeKit package * in Windows, using the Control Panel-Add/Remove Programs applet * in Linux, using the command safekit uninstall Uninstalling SafeKit includes creating a backup of the installed modules in SAFE/Application\_Modules/backup, then unconfiguring them. 6.    Undo all configurations that you have done manually for the firewall setup #### 4.1.1.3       Post-uninstall operations On each node, save the cluster configuration and clean some directories: 1.    Delete the directory SAFE/modules/ 2.    Delete the directory SAFEVAR 3.    Delete the directories SAFE/web and SAFE/snmp Warning: when upgrading from SafeKit 7.5, your previous password to log in the web console will be lost. #### 4.1.1.4       New SafeKit 8.2 package install This is the quick install and setup procedure. For details, see “SafeKit install” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf). On each node: 1.    Install the package | | | | --- | --- | | **Windows** | **Linux** | | a.    Log as administrator b.    Double click on the package safekitwindows\_8\_2\_y\_z.msi c.    Open a PowerShell console d.    To setup the Windows firewall, run: cd SAFE\private\bin\ .\firewallcfg add e.    To initialize the web service with the admin user and its password, for instance, pwd, run cd SAFE\private\bin\ .\webservercfg.ps1 -passwd pwd   | | | | --- | --- | | Commentaire, ajouter contourCommentaire, ajouter contour | Since SafeKit 8.2.3, at the end of the SafeKit install, the wizard offers to proceed with steps d and e. | | a.    Log as root b.    Open a system console c.    Run chmod +x safekitlinux\_8\_2\_y\_z.bin d.    Run ./safekitlinux\_8\_2\_y\_z.bin It extracts the package and the safekitinstall script e.  Run ./safekitinstall ·         Reply yes for firewall automatic configuration (with firewalld or iptables) ·         Reply with the password, for instance, pwd to initialize the web service with the admin user | | | | | | --- | --- | | Commentaire important contourCommentaire important contour | The password must be identical on all nodes that belong to the same SafeKit cluster. Otherwise, web console and distributed commands will fail with authentication errors. | | |   The last step is for initializing the web service that relies by default, since SafeKit 7.5, on user authentication. Once this initialization is done on all the cluster nodes: ·         you can authenticate in the web console with the name admin and the password you provided.  The role is Admin by default. ·         you can run distributed command safekit -H … Skip this initialization if you want to setup another configuration for the web service. For other setups, see section “Securing the SafeKit web service” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf). 2.    For using the web console, clear the browser cache with CTRL and SHIFT while tapping the DELETE key 3.    Check with the command safekit level the installed SafeKit version and the validity of the license (which has not been uninstalled) #### 4.1.1.5       Migration operations for the web service In the previous release of SafeKit, you may have modified the default configuration of the web service to customize it to your needs. In that special case, you should have saved the directory SAFE/web in step 4 of [section](#_Pre-upgrade_operations) 4.1.1.1. In SafeKit 8.2, the configuration of the web service has evolved. Carrying over your old configuration to the new version of SafeKit may require some adaptations. For details on the default setup and all predefined setups, see section “Securing the SafeKit web service” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf). For HTTPS and login/password configurations, certificates and user.conf/group.conf generated for the previous release are still supported. | | | | --- | --- | | Commentaire important contourCommentaire important contour | On Linux, for all files added under SAFE/web/conf, change their rights with: chown safekit:safekit SAFE/web/conf/ chown safekit:safekit SAFE/web/conf/ssl/httpd.webconsolessl.conf (when configured for HTTPS) | #### 4.1.1.6       Migration operations for the SNMP agent In the previous release of SafeKit, you may have modified the default configuration of the SNMP agent to customize it to your needs. In that special case, you should have saved the directory SAFE/snmp in step 4 of [section](#_Pre-upgrade_operations) 4.1.1.1. In SafeKit 8.2, the configuration of the SNMP agent has evolved. Carrying over your old configuration to the new version of SafeKit may require some adaptations. For details see section “SNMP monitoring” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf). It also details how to manage the SNMP agent in SafeKit 8.2. #### 4.1.1.7       Migration operations for the cluster configuration From one node: 1.    Log as administrator/root 2.    Open a PowerShell/shell console 3.    Configure the cluster * Edit cluster.xml saved into your backup folder and remove: o         console=”on” or console=”off” o         framework=”on” or framework=”off” o         connect=”on” or connect =”off” These attributes are obsolete from SafeKit 8.2 web console. * Copy the saved cluster.xml file into SAFE/var/cluster/ * Apply the cluster configuration on all nodes with safekit cluster config safekit -H ”\*” -G * Check the cluster configuration is consistent (same signature for all nodes) safekit -H ”\*” cluster confinfo #### 4.1.1.8       Migration operations for the modules From one node: 1.    Log as administrator/root 2.    Open a PowerShell/shell console 3.    Install the modules Old installed modules must be re-installed with: ·         their configuration saved into SAFE/Application\_Modules/Backup Select the last saved configuration for the module (.safe file with the module name as prefix) ·         their module id that you have noted in step 3 of [section](#_Pre-upgrade_operations) 4.1.1.1. The module id is necessary only if you have more than one module and if the value of the communication ports used by the module is important in your environment. For instance, to re-install the AM module with the saved configuration SAFE/Application\_Modules/Backup/AM.safe and the id 2, run: safekit module install -M 2 -m AM SAFE/Application\_Modules/Backup/AM.safe 4.    Configure the modules If the module was configured to automatically start at boot, change the module configuration to insert the attribute boot=”on” (see [section](#_Module_boot_configuration)  2.3.4.1). Since SafeKit 7.5, this option replaces the command safekit boot –m AM. If the module is configured with a custom checker, change the module configuration to insert the attribute action="wait", "stop", "stopstart" or "restart" and remove the section (see [section](#_Custom_checker_simplification) 2.1.5). At this step, module can be re-configured either with the web console or commands: ·         create cryptographic for the module if necessary safekit module genkey –m AM ·         configure and export the module on node1 and node2 (node name in cluster.xml) safekit -H "node1,node2" -E AM note: if the module must be configured on all nodes of the cluster.xml you can run safekit -H "\*" -E AM 5.    Start the modules To restart modules after the upgrade: ·         farm module safekit start –m AM (replace AM by the module name) ·         mirror module o         On the server that has the up-to-date replicated files (former PRIM or ALONE): safekit prim –m AM (replace AM by the module name) o         On the other server (former SECOND): safekit second –m AM (replace AM by the module name) ## 4.2      Migrating from SafeKit 7.5.1 to SafeKit 7.5.2 SafeKit 7.5.2 is compatible with SafeKit 7.5.1. Therefore, it is a minor upgrade, and the nodes upgrade order can the one described in [section](#_Minor_upgrade) 1.2.1. The upgrade procedure for one node is the standard one described in the *SafeKit upgrade* section of the *SafeKit User’s* Guide. ## 4.3      Migrating from SafeKit 7.4.0 to SafeKit 7.5.1 Since SafeKit 7.5, some changes into protocol imply that this release is not compatible with older releases. Therefore, it is a major upgrade that requires to stop and upgrade nodes at the same time when migrating to release 7.5. This is detailed in [section](#_Major_upgrade) 1.2.2. Moreover, SafeKit 7.5 comes with a major change in internal data storage and web service. You cannot apply the standard procedure but only the one described below. ### 4.3.1          Upgrade procedure SafeKit is installed in: | | | | | --- | --- | --- | | | Windows if %SYSTEMDRIVE%=C: | Linux | | SAFE | C:\safekit | /opt/safekit | | SAFEVAR | C:\safekit\var | /var/safekit | #### 4.3.1.1       Pre-upgrade operations On each node to migrate: 1.    Note the state "on" or "off" of services and modules started automatically at bootsafekit boot webstatus; safekit boot snmpstatus; safekit boot status -m AM (where AM is the name of the module) 2.    For a mirror module Note the server in the ALONE or PRIM status to know which server holds the up-to-date replicated files 3.    Run the command safekit module listid to know the installed modules and note their ids 4.    Optionally, take snapshots of modules Uninstalling/reinstalling will reset SafeKit logs and dumps of each module. If you want to keep this information (logs and last 3 dumps and configurations), run the command safekit snapshot –m AM /path/snapshot\_xx.zip (replace AM by the module name) #### 4.3.1.2       Old SafeKit package uninstall On each node to migrate: 1.    Log as administrator/root 2.    Open a PowerShell/shell console 3.    Stop all modules using the command safekit shutdown For a mirror in the PRIM-SECOND status, stop first the SECOND server to avoid an unnecessary failover 4.    Close all editors, file explorers, shells, or terminal under SAFE and SAFEVAR (to avoid package uninstallation error) 5.    Uninstall the SafeKit package * in Windows, using the Control Panel-Add/Remove Programs applet * in Linux, using the command safekit uninstall 6.    undo all configurations that you have done manually for the firewall setup   Uninstalling SafeKit includes creating a backup of the installed modules in SAFE/Application\_Modules/backup, then unconfiguring them. #### 4.3.1.3       Post-uninstall operations On each node, save the cluster configuration and clean some directories: 1.    Copy the file SAFEVAR/cluster.xml in another directory 2.    Delete the directory SAFE/modules/ 3.    Delete the directory SAFEVAR #### 4.3.1.4       New SafeKit 7.5 package install This is the quick install and setup procedure. For details, see “SafeKit install” in in the *SafeKit User’s Guide*. On each node: 1.    Install the package | | | | --- | --- | | **Windows** | **Linux** | | f.     Log as administrator g.    Double click on the package safekitwindows\_7\_5\_y\_z.msi h.    Open a PowerShell console i.     To setup the Windows firewall, run: cd SAFE\private\bin\ .\firewallcfg add j.     To initialize the web service with the admin user and its password, for instance, pwd, run cd SAFE\private\bin\ .\webservercfg.ps1 -passwd pwd | f.     Log as root g.    Open a system console h.    Run chmod +x safekitlinux\_7\_x\_y\_z.bin i.     Run ./safekitlinux\_7\_x\_y\_z.bin It extracts the package and the safekitinstall script j.  Run ./safekitinstall ·         Reply yes for firewall automatic configuration (with firewalld or iptables) ·         Reply with the password, for instance, pwd to initialize the web service with the admin user | | | | | | --- | --- | | Commentaire important contourCommentaire important contour | The password must be identical on all nodes that belong to the same SafeKit cluster. Otherwise, web console and distributed commands will fail with authentication errors. | | |   The last step is for initializing the web service that relies by default, since SafeKit 7.5, on user authentication. Once this initialization is done on all the cluster nodes: o    you can authenticate in the web console with the name admin and the password you provided.  The role is Admin by default. o    you can run distributed command safekit -H … Skip this initialization if you want to setup another configuration for the web service. For other setups, see section “Securing the SafeKit web service” in the *SafeKit User’s Guide*. 2.    If you use the web console, clear the browser cache with CTRL and SHIFT while tapping the DELETE key 3.    Check with the command safekit level the installed SafeKit version and the validity of the license (which has not been uninstalled) #### 4.3.1.5       Migration operations for the web service In the previous version of SafeKit, you may have modified the default configuration of the web service to customize it to your needs. In that special case, the customized files in SAFE/web/conf/ have been saved in SAFE/web/conf/.conf.. Since SafeKit 7.5, the configuration of the web service has evolved. Carrying over your old configuration to the new version of SafeKit may require some adaptations. For details on the default setup and all predefined setups, see section “Securing the SafeKit web service” in the *SafeKit User’s Guide*. #### 4.3.1.6       Migration operations for the cluster configuration From one node: 1.    Log as administrator/root 2.    Open a PowerShell/shell console 3.    Configure the cluster * Copy the saved cluster.xml file into SAFE/var/cluster/ * Apply the cluster configuration on all nodes with safekit cluster config safekit -H ”\*” -G * Check the cluster configuration is consistent (same signature for all nodes) safekit -H ”\*” cluster confinfo #### 4.3.1.7       Migration operations for the modules From one node: 1.    Log as administrator/root 2.    Open a PowerShell/shell console 3.    Install the modules Old installed modules must be re-installed with: ·         their configuration saved into SAFE/Application\_Modules/Backup Select the last saved configuration for the module (.safe file with the module name as prefix) ·         their module id that you have noted in step 4.3.1.1. The module id is necessary if the value of the communication ports used by the module is important in your environment.   For instance, to re-install the mirror module with the saved configuration SAFE/Application\_Modules/Backup/mirror.safe and the id 2, run: safekit module install -M 2 -m mirror SAFE/Application\_Modules/Backup/mirror.safe 4.    Configure the modules If the module was configured to automatically start at boot, change the module configuration to insert the attribute boot=”on” (see [section](#_Module_boot_configuration) 2.3.4.1). This option replaces the command safekit boot –m AM. At this step, module can be re-configured either with the web console or commands: ·         create cryptographic for the module if necessary safekit module genkey –m AM ·         configure and export the module on node1 and node2 (node name in cluster.xml) safekit -H "node1,node2" -E AM 5.    Start the modules To restart modules after the upgrade: ·         farm module web console/![control16](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2010%2010'%3E%3C/svg%3E)![control16](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image013.png) Control/![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2038%2010'%3E%3C/svg%3E)![](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image023.jpg) on the module/![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2010%2010'%3E%3C/svg%3E)![](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image024.png) Start/ or command line safekit start –m AM (replace AM by the module name) ·         mirror module On the server that has the up-to-date replicated files (former PRIM or ALONE): web console/![control16](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2010%2010'%3E%3C/svg%3E)![control16](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image013.png) Control/![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2038%2010'%3E%3C/svg%3E)![](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image023.jpg) on the node/Expert/Force start/as prim/ or command line safekit prim –m AM (replace AM by the module name) On the other server (former SECOND): web console/![control16](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2010%2010'%3E%3C/svg%3E)![control16](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image013.png) Control/![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2038%2010'%3E%3C/svg%3E)![](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image023.jpg) on the node/Expert/Force start/as second/ or command line safekit second –m AM (replace AM by the module name) ### 4.3.2          Configuration of the module boot start Before SafeKit 7.5, the configuration to start the module at boot was done with the command safekit boot -m AM on | off (which had to be executed on each node). Since SafeKit 7.5, this configuration is included into the module configuration. This simplifies the configuration on both nodes and preserves the configuration on SafeKit upgrade. For details, see [section](#_Module_boot_configuration) 2.3.4.1.