KB484970: "Platform Analytics back up false" errors occurs when running the MSTRBak tool

Quality Engineer, Senior • MicroStrategy

This article provides a solution to avoid the Platform Analytics backup failure when using the MSTRbak tool to back up your environment.

Description

Using the MSTRBak tool to back up your environment may result in the following error when backing up Platform Analytics:
Platform Analytics back up false

Solution

Check if the database user has privilege to assess all the tables in the database. If not, change the database user to one who has higher privilege.
Ping the database host in the machine where you are running MSTRBak to check the connectivity to the database host.
Check if the bin path is set correctly:

For Strategy 2019, the MySQL bin path format is
```
/usr/bin
```
.
For MySQL driver, only
```
mysql-connector-java-8.0.x.jar
```
is supported. You are recommended to use
```
mysql-connector-java-8.0.12.jar
```
or
```
mysql-connector-java-8.0.18.jar.
```
For Strategy 2020 and later, the PostgreSQL bin path format is
```
/install/Repository/bin.
```

Run MSTRBak in dump mode, e.g.,
```
./mstrbak -d
```

For Strategy 2019, run the following MySQL dump command under the bin path:


./mysqldump -h [hostname] -u [username] -pPASSWORD --single-transaction --databases platform_analytics_wh > platform_analytics_wh.sql

For Strategy 2020 and later, run the following PostgreSQL dump command under the bin path:
```
./mstr_pg_dump -d platform_analytics_wh -h [hostname] -p 5432 -U [username] -f platform_analytics_wh.sql
```
If successful, then please contact the Strategy Support team.
If it fails, contact the Database team. After this issue is fixed, run the MSTRBak tool again and check if Platform Analytics can be successfully backed up.

If the above methods do not solve the problem, contact the Strategy Support team with the following logs:

~/Mstrbak-client/logs/MSTRBAK - BACKUP.log

```
~/Mstrbak-client/DBMigratorLogger.log
```
```
/log/MACmdMgrW.xml
```

Comment

0 comments

Details

Knowledge Article

Published:

April 8, 2021

Last Updated:

April 8, 2021

Solution

Check if the database user has privilege to assess all the tables in the database. If not, change the database user to one who has higher privilege.

Ping the database host in the machine where you are running MSTRBak to check the connectivity to the database host.

Check if the bin path is set correctly:

For Strategy 2019, the MySQL bin path format is
```
/usr/bin
```
.
For MySQL driver, only
```
mysql-connector-java-8.0.x.jar
```
is supported. You are recommended to use
```
mysql-connector-java-8.0.12.jar
```
or
```
mysql-connector-java-8.0.18.jar.
```
For Strategy 2020 and later, the PostgreSQL bin path format is
```
/install/Repository/bin.
```

Run MSTRBak in dump mode, e.g.,

./mstrbak -d

For Strategy 2019, run the following MySQL dump command under the bin path:


./mysqldump -h [hostname] -u [username] -pPASSWORD --single-transaction --databases platform_analytics_wh > platform_analytics_wh.sql

For Strategy 2020 and later, run the following PostgreSQL dump command under the bin path:
```
./mstr_pg_dump -d platform_analytics_wh -h [hostname] -p 5432 -U [username] -f platform_analytics_wh.sql
```
If successful, then please contact the Strategy Support team.
If it fails, contact the Database team. After this issue is fixed, run the MSTRBak tool again and check if Platform Analytics can be successfully backed up.

If the above methods do not solve the problem, contact the Strategy Support team with the following logs:

~/Mstrbak-client/logs/MSTRBAK - BACKUP.log

```
~/Mstrbak-client/DBMigratorLogger.log
```
```
/log/MACmdMgrW.xml
```