Last verified version: AMC 3.2.1, AAC 4.4.2
Last update:
Overview
This article guides you through migrating your ASGARD Management Center to a new server. It also serves as a basis for other ASGARD products or disaster recovery.
The ASGARD version used to create the backup must match the version where it is imported.
Prerequisites
-
Access to our https://portal.nextron-systems.com/ .
-
A valid, activated ASGARD license.
-
Console root and web access to your server.
-
A management center with the latest version.
-
A current backup of your legacy Management Center.
-
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 Master ASGARD 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 Master ASGARD.
-
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 an virtualized ASGARD 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 ASGARD Products Without Nextron Installer CD in Azure .
Please inform us about your migration project, as unwanted license usage can occur in certain constellations with regard to the asset licenses.
Related Content
- Fixing Time Zone Issues in ASGARD Management Center for Scheduled THOR Scans
- Repairing Broken Permissions of ASGARD Agent in Windows
- Fixing FQDN Issues for ASGARD Installation and Connectivity
- Avoiding Multiple Asset Requests in Restricted Endpoint Configurations
- Troubleshooting Cluster Health Check Issues After Updating Elastic Search Cluster Member