Version 2020

1. MicroStrategy Backup Preparations

Before you begin the upgrade with MicroStrategy Backup, take care of the following item:

  • Intelligence Server must run on a Linux Operating System (preferably Red Hat Enterprise Linux or equivalent).
    • If you intend to restore an archive onto MicroStrategy Cloud Platform for AWS or MicroStrategy Cloud Platform for Azure:
      • Switching from an Enterprise environment to a Team or Department environment only allows you to choose a maximum of two nodes to back up cubes and caches. Be aware of the differences in RAM usage when moving from a different environment.
      • Ensure you have an S3 bucket or Azure Storage Account (with Standard Performance Type) set up.
      • Remove any metadata password complexity restrictions forcing special characters. This process does not support passwords with special characters as it must be unified across multiple applications and the restored deployment will fail. For more information regarding password complexity restrictions, see KB34105.

Be aware of the restrictions of MicroStrategy Backup:

  • MicroStrategy metadata can be on a MySQL or PostgreSQL database. MicroStrategy environments prior to MicroStrategy 2020 use MySQL. MicroStrategy environments 2020 and onward use PostgreSQL.
  • Additional flat files will be restored to a single directory. The back up and restoration of files requires your discretion.
  • Additional DSNs require the same credential and server location as the metadata.
  • You can only back up a maximum of four nodes in a cluster.
  • You cannot back up OS configurations, such as timezone and heap size.

Once you have the above settings and installations, you can begin installing MicroStrategy Backup.