EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB484972: "Metadata is required to be backed up" error occurs when running the MSTRBak tool


Lilin Yu

Quality Engineer, Senior • MicroStrategy


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

Description


When using the MSTRBak tool to back up your environment, the following error occurs when backing up the metadata:
Metadata is required to be backed up

Solution

  • Check if the database has write permission to the directory where you want to save the bak file, e.g.,
    /opt/mstr/mstrbak
    . 
ka04W000001EthAQAS_0EM4W0000027LL7.jpeg
  • Ping the database host in the machine where you are running MSTRBak to check the connectivity to the database host.
  • Check if the database user has privilege to access all the tables in the database. If not, change the database user to one who has higher privilege. 
  • Check if the bin path is set correctly:
    • PostgreSQL bin path format is
      <MSTR install path>/install/Repository/bin.
    • 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.

  • If the metadata database type is NOT mySQL or PostgreSQL, there is no credential check after inputting your credentials, so double-check your database credential. 
  • Run MSTRBak in dump mode, e.g.,
    ./mstrbak -d

    • For MySQL, run the following dump command under the bin path:
      
      ./mysqldump -h [hostname] -u [username] -pPASSWORD --single-transaction --databases [database name] > xxxx.sql
      

    • For PostgreSQL, run the following dump command under the bin path:
      
      ./mstr_pg_dump -d [database name] -h [hostname] -p 5432 -U [username] -f xxxx.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