Migrating customizations with the PATROL Configuration Manager

PATROL Configuration Manager allows you to manage customizations to KMs, depending on the type of customization. Before migrating any changes to the KMs, you should review Using PATROL Configuration Manager with PATROL for Microsoft SQL Server

• If you have localized parameters or global parameters that have customized poll times or thresholds, use the AS_CHANGESPRING KM to migrate these customizations into PATROL Configuration Manager rulesets as described in the PATROL Configuration Manager User Guide and in Using PATROL Configuration Manager with PATROL for Microsoft SQL Server
• If you have created custom recovery actions, follow these steps:
  1. Ensure that you have made a record of your customizations and have backed up the customized files in the PATROL_HOME and PATROL_CACHE directories.
  2. Uninstall the old version of PATROL for Microsoft SQL Server.
  3. Install the new version of PATROL for Microsoft SQL Server as described in the section Installing for the first time or upgrading over an existing installation.
  4. Ensure that you have made a record of your custom recovery actions.
  5. Use the Recovery Action Event Management commands as described in the PATROL Configuration Manager User Guide to migrate your custom recovery actions to the PATROL Configuration Manager.