How to Obtain MicroStrategy Backup Inputs

This is any location on the Linux or Windows machine where the backup file is written.

By default, on cloud environments it is /opt/mstr/MicroStrategy/.

If this is not the correct path, you can find the path by running locate MSIReg.reg as this file will only exist in the MicroStrategy install path.

Open the MSIReg.reg file in your text editor and search for ServerInstanceName.

Open Project Configuration for one of your projects and choose Intelligent Cubes > General. The path appears in the top window beginning with MSTRInstallPath.

For example,./Cube/env-31097laiouse1 = /opt/mstr/MicroStrategy/Cube/env-laiouse1

Open Project Configuration for one of your projects and choose Caching > Result Caches > Storage. The path appears in the top window beginning with MSTRInstallPath.

For example, ./Caches/env-31097laiouse1 = /opt/mstr/MicroStrategy/Caches/env-laiouse1

Most often it will be in /tomcat/{version}/webapps/MicroStrategyMobile/WEB-INF/xml/mobile.

Most often it will be in /tomcat/{version}/webapps/MicroStrategy/WEB-INF/xml/sys_defaults.properties.

Most often it will be in /tomcat/{version}/webapps/MicroStrategyLibrary/images.

Most often it will be in /tomcat/{version}/webapps/MicroStrategyMobile/images.

Most often it will be in /tomcat/{version}/webapps/MicroStrategy/images.

Most often it will be in /tomcat/{version}/webapps/MicroStrategyLibrary/plugins.

Most often it will be in /tomcat/{version}/webapps/MicroStrategyMobile/plugins.

Most often it will be in /tomcat/{version}/webapps/MicroStrategy/plugins.

Run the command which mysqldump as root.

Run the command which mongodump as root.

Open the MSIReg.reg file and search Location. Use the location in [HKEY_LOCAL_MACHINE\SOFTWARE\MicroStrategy\Data Sources\CastorServer].

Open the Intelligence Server Configuration in Developer. Take note of the Database Instance name. Close the Intelligence Server Configuration and choose Administration > Configuration Managers > Database Instances. Right-click and edit the database instance you found in the Intelligence Server Configuration. Click Modify. The HistoryListDSN is the name of the ODBC data source in the Database Connections window.

This is the username of an administrator user in the database.

This is the password of an administrator user in the database.

The username of a metadata user with full administrative privileges (Administrator is recommended).

The password of a metadata user with full administrative privileges (Administrator is recommended).

List the names of any additional DSNs that will be needed in the new environment. These names can be found in the odbc.ini file located in the MSTRInstallPath.

For all projects, enter *. For multiple projects, add brackets with each project name in quotations separated by commas.

For example, [“MicroStrategy Tutorial”, “Enterprise Manager”]

Open License Manager on the Intelligence Server machine and open Audit. Note the project source that connects the Intelligence Server. If there is not a project source, create one using the Configuration Wizard.

Enter Yes or No. Enter Yes to upload the MicroStrategy Backup file to AWS S3 or Azure Blob.

This is the name of the S3 bucket (without S3://).

The S3 access key used to access the S3 bucket.

The S3 secret key used to access the S3 bucket.

This is the name of the Storage Account in Azure.