Preparing for upgrade
Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the current installation. If the .kml file or any of the .km files for the new version of PATROL for Windows Servers has a different file name from the previous version, you must remove those files from the list of KMs that are preloaded on the PATROL Agent.
Before you begin
If you plan to migrate your customizations, determine whether you can migrate from a previous version of PATROL for Windows Servers. See Versions that you can migrate to determine whether migration is supported for your current version of PATROL for Windows Servers.
Back up the current installation
Back up your customizations so that you can restore the current installation if you want to roll back your upgrade.
- Shut down any PATROL Agents, consoles, and related services that are currently running.
- Ensure that no one is accessing any PATROL files or directories.
- Perform a full backup of the directories where PATROL files are typically stored. These directories are listed in the following table:
File type | Directory |
|---|---|
executables and data | PATROL_HOME for agent and console installation directories |
console customizations | PATROL_CACHE for the console working cache |
The following topics help you prepare for the upgrade:
- Determining whether you can migrate KM customizations
- Automatic migration of console and agent customizations
- Migrating customizations with the PATROL Configuration Manager
- Determining the location of PATROL
- Creating an installation package of the migrated and merged KM
- Moving files from the PATROL_CACHE directories