Internal documentation only
This page has been marked as draft.
Migration Guide
Here is a guide that you can use for reference in your migration, it should be done in separate steps to validate all is working as expected during the process Copied
-
Migrate the License daemon. This component is the easiest to migrate, as it can be installed separately in the new server with a new license file. You will need to request a new license for the new server to us (Support) that mimics the old license.
-
**Connect to new license daemon.**Connect old gateway to the new license daemon.
-
Decommission old license daemon.
-
**Gateway migration.**There are two possible approaches:
-
Full migration at once. Gateway can be migrated all at once by installing the new gateway binaries in the new server and then copying the main gateway setup file, the includes files and any gateway scripts over.
-
Gradual migration by components.You can create a new Gateway and migrate the configuration gradually from the old to the new one. This approach is slower but safer as allows to test each migrated component or partially rollback in case of issue.
-
Important notes: Copied
- Make sure there is no connectivity issue between gateway and licd and netprobes, and the new server has access to all the required components that is monitoring.
- If this is a hot stand-by set up, run gateway up as standalone first, then enable hot-standby when everything is ready.
- During the migration, both new and old gateways can coexist.