Version 2021

1. MicroStrategy Backup Preparations

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

  • Intelligence server must run on a supported operating system. See Platform Certifications for more information.

  • If you intend to restore an archive onto MicroStrategy Cloud Platform for AWS or MicroStrategy Cloud Platform for Azure:

    • Windows only: LDAP must be re-configured in the new destination environment.

    • Windows only: wget and tar commands must be installed on the Windows machine.
    • 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. For more information regarding password complexity restrictions, see KB34105.

Be aware of the restrictions of MicroStrategy Backup:

  • MicroStrategy metadata can be on a MySQL, PostgreSQL, Oracle, or SQL server. See Platform Certifications for a list of supported databases.

  • Asymmetric clustering is backed up based on the node you choose and requires your discretion on the configurations.
  • Additional flat files will be restored to a single directory. After restoring, you can find those files in the default path: /opt/mstr/mstrbak/additional_files.
  • You can only back up a maximum of four nodes in a cluster.
  • Restore to MicroStrategy AWS and Azure supports a maximum of four nodes.

  • 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.