Last verified version: MC 3.2.1, AC 4.4.2
Last update:
Please inform us about your migration project, as unwanted license usage can occur in certain constellations with regard to the asset licenses.
Overview
This article guides you through migrating your Management Center to a new server. It also serves as a basis for other products or disaster recovery.
Prerequisites
The version used to create the backup must match the version where it is imported.
-
Access to our https://portal.nextron-systems.com/ .
-
A valid, activated license.
-
Console root and web access to your server.
-
A Management Center with the latest version. See https://asgard-manual.nextron-systems.com/en/latest/changelog/index.html
-
A current backup of your legacy Management Center. See https://asgard-manual.nextron-systems.com/en/latest/maintenance/backup-restore.html
-
Systems communicate via FQDN resolution using DNS. See https://asgard-manual.nextron-systems.com/en/latest/requirements/network.html# .
-
No scans or tasks running from the legacy Management Center or Management Center (Controller) during migration.
Expected result
-
The Management Center can be accessed via the web UI.
-
The asset agents can communicate with the Management Center.
-
The Management Center can communicate with the Analysis Cockpit and Management Center (Controller).
-
The Management Center can obtain updates.
-
The initial configuration has been successfully applied.
Steps to proceed
If a migration is required and it can´t be performed via import and export of a virtualized Management Center instance, we have to distinguish between two scenarios:
If you can´t use our Universal Installer ISO (e.g. for Azure), please refer to Installing Nextron Products Without Nextron Installer CD in Azure .
Related Content
- Migrating or Recovering the Analysis Cockpit to a New Server
- Managing Disk Space in Analysis Cockpit: Safe and Unneeded File Deletion Options
- Fixing Time Zone Issues in Management Center for Scheduled THOR Scans
- Repairing Broken Permissions of Endpoint Agent in Windows
- Fixing FQDN Issues for Management Center Installation and Connectivity