Upgrade FAQs

Can i keep my current system running while testing the upgrade ?

The short answer is Yes.

The actual process is more nuanced than that. You will need to take an image of the current system modify it offline to prevent it clashing with the old and then upgrade the image. You can also do it the other way by upgrading the system and then restoring the backup disk image.

Should i run my current system and a new system in parallel ?

The short answer is No

The migration process is written for immediate cut over.

You should already have a test enviroment, carrying non mission critical domain traffic in place where you can test changes. On completion of change refinement in the testing enviroment you can apply those processes in your production enviroment.

What does the restore script actually do ?

  • The script shuts down database access to ensure your can return to the point in time.
  • Drops objects from the database that cannot be migrated (Python2)
  • Takes a backup of the database in this state that is importable.
  • Shuts down the database itself.
  • Shuts down any remaining services.
  • Writes out a script that can be used to bootstap a new system.

Can i use a system on which the restore script has been run ?

No, the system should not be used after the restore script has been run.

  1. The database is not in the original state as some objects have been dropped.
  2. The new generated data will be lost when the original restore is run.
  3. Running parallel systems means data loss is inevitable.

Do i need a new activation key for the upgrade ?

No, your current activation key will be usable.

Can the activation key remain active on both hosts ?

Yes, using your currect activation key in an upgrade will not disable your current system.