Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

EMS Administration Guide

Migrating to another EMS instance

You can simply and efficiently move configurations, data, and endpoint connections between EMS instances without disrupting FortiClient endpoint functionality. This document describes migrating one EMS on-premise environment to another. This migration requires the following:

  • The EMS version in both environments is 6.4.3 GA.
  • FortiClient for all supported endpoint platforms (Windows, macOS, Linux, Android, and iOS) are connected before, during, and after migration.
  • You have fully configured EMS and generated data such as logs and events before starting the migration.
  • Licensing on the two EMS instances is similar, if not the same, in terms of the number of seats, entitlement, license types, and duration.

This guide refers to the EMS instance that you are migrating from as "EMS A". It refers to the EMS instance that you are migrating to as "EMS B".

To migrate from EMS A to EMS B:
  1. Install and license EMS B as Installation and licensing describes.
  2. Back up the EMS A database as To back up the database: describes.
  3. Restore the database on EMS B as To restore the database: describes.
  4. Migrate the FortiClient endpoints. This migration process supports all FortiClient endpoint platforms, except Chromebook:
    1. On EMS A, go to Endpoints.
    2. Select the desired endpoints to migrate.
    3. Select Action > Switch EMS > Choose a Different IP.

    4. In the dialog, enter the EMS B FQDN or IP address. Once the migration begins, the Connections column on the Endpoints pane in EMS B for the selected endpoints displays as Migrating. Events may not display immediately on the Endpoints pane in EMS B, but are present in the database. Endpoints that are offline when you apply the Choose a Different IP action migrate when they reconnect to EMS A.

    5. Shut down EMS A.
    6. For any remaining endpoints that have not been migrated, manually connect them to EMS B by entering the EMS B IP address on the Zero Trust Telemetry tab. See Connecting FortiClient Telemetry after installation.
    7. Monitor EMS B services and system performance to ensure stability.

Limitations

  • Chromebook: The migration does not support migration for Chromebook endpoints.

Migrating to another EMS instance

You can simply and efficiently move configurations, data, and endpoint connections between EMS instances without disrupting FortiClient endpoint functionality. This document describes migrating one EMS on-premise environment to another. This migration requires the following:

  • The EMS version in both environments is 6.4.3 GA.
  • FortiClient for all supported endpoint platforms (Windows, macOS, Linux, Android, and iOS) are connected before, during, and after migration.
  • You have fully configured EMS and generated data such as logs and events before starting the migration.
  • Licensing on the two EMS instances is similar, if not the same, in terms of the number of seats, entitlement, license types, and duration.

This guide refers to the EMS instance that you are migrating from as "EMS A". It refers to the EMS instance that you are migrating to as "EMS B".

To migrate from EMS A to EMS B:
  1. Install and license EMS B as Installation and licensing describes.
  2. Back up the EMS A database as To back up the database: describes.
  3. Restore the database on EMS B as To restore the database: describes.
  4. Migrate the FortiClient endpoints. This migration process supports all FortiClient endpoint platforms, except Chromebook:
    1. On EMS A, go to Endpoints.
    2. Select the desired endpoints to migrate.
    3. Select Action > Switch EMS > Choose a Different IP.

    4. In the dialog, enter the EMS B FQDN or IP address. Once the migration begins, the Connections column on the Endpoints pane in EMS B for the selected endpoints displays as Migrating. Events may not display immediately on the Endpoints pane in EMS B, but are present in the database. Endpoints that are offline when you apply the Choose a Different IP action migrate when they reconnect to EMS A.

    5. Shut down EMS A.
    6. For any remaining endpoints that have not been migrated, manually connect them to EMS B by entering the EMS B IP address on the Zero Trust Telemetry tab. See Connecting FortiClient Telemetry after installation.
    7. Monitor EMS B services and system performance to ensure stability.

Limitations

  • Chromebook: The migration does not support migration for Chromebook endpoints.