DE 

//Cloudogu EcoSystem Docs

  1. docs.cloudogu.com
  2. User manual
  3. Automatic Migration
  4. Reference
  5. Prerequisites
Getting Started
User manual
Developer documentation

Prerequisites

The source and target instances must fulfill a number of prerequisites for successful migration.

Prerequisites for the source instance

  • Port 7022 and port 80 are accessible from outside.
  • The minimum version of the installed Dogus corresponds to this list
  • All Dogus are healthy

  • The instance is in export mode.

    • A CES-VM instance is in export mode when all Dogus are "healthy".
    • A CES-MN instance is in export mode when the "exportCron" timestamp is in the past.

Minimal dogu versions

  • nginx: 1.28.0-2

Requirements of the target instance

  • The available free memory is dimensioned so that the volumes can be increased to the data volume of the source instance plus the configured factor.
  • All Dogus are healthy
  • The aforementioned ports on the source instance must be reachable from the target instance.

Further requirements

Backup schedules

The backup operator is optional for migration.

  • If there are no backup schedules or the backup operato is not available on the source instance, the importer skips the import of backup schedules. Existing backup schedules on the target instance remain unchanged.
  • If backup schedules are provided but the BackupSchedule API is not available on the target instance, the importer skips the import of backup schedules. Configuration and data migration can continue if the other prerequisites are met.
  • If backup schedules are provided and the BackupSchedule API is available on the target instance, the importer creates the schedules or replaces existing schedules with the same names.

The requirements for components still apply. All components of a CES-MN source instance must be installed in the same version on the target instance. This also applies to backup components installed on the source instance. Additional target components are allowed.

Dogus

  • The Dogu versions of the source and target instances must match exactly.

  • These dogus are an exception:

    • The nginx dogu of the CES-VM is not deployed in CES-MN. There is the nginx-static and the nginx-ingress for this.
    • The migration takes this into account automatically.
    • The Backup & Restore dogu only exists in the CES-VM. The functions are mapped in the CES-MN by other applications.
    • This dogu should not be deleted!
    • The migration automatically takes this into account.
    • Jira and Confluence are no longer supported in CES-MN.
    • These dogus must be deleted on the source instance before migration.
    • The Monitoring dogu (official/monitoring) is ignored during migration as it does not exist in CES-MN.
    • The functions of the Monitoring-Dogu are taken over by Grafana in CES-MN. For technical reasons, Grafana may only be installed after the migration has been completed.
    • The migration takes this into account automatically.
    • The Registrator-Dogu no longer exists in CES-MN.
    • The migration takes this into account automatically.