Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5692

mcs_backup_manager | dbrm_restore

    XMLWordPrintable

Details

    • New Feature
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • cmapi
    • None

    Description

      The purpose of this feature is to help automate the restore of columnstore internal metadata and visualize the options to restore from dbrm_backups.
      Best for single nodes, works with mulitnode but would need to the manually coordinate the stop/start of mariadb & cmapi on the two replica nodes that the bash script cant reach.

      Reproduction

      wget https://raw.githubusercontent.com/mariadb-corporation/mariadb-columnstore-engine/develop/extra/cs_package_manager.sh; chmod +x cs_package_manager.sh;
      time bash cs_package_manager.sh install enterprise 10.6.14-9 --token xxxxxxx
      # optional: 2-MCOL-5637-setup-s3.sh
       
      bash mcs_backup_manager.sh dbrm_backup
      mariadb -e "create database if not exists test; use test;"
      mariadb test -e "CREATE TABLE test_table( group_name CHAR(2), number1 DECIMAL(12, 2), number2 DECIMAL(12, 2), var varchar(1)) ENGINE=COLUMNSTORE;" 
      mariadb  test -e "INSERT INTO test_table SELECT CAST(ROUND(RAND() * 10, 0) AS CHAR), ROUND(RAND() * 1000000, 2), ROUND(RAND() * 1000, 2), substring(MD5(RAND()),1,1) FROM seq_1_to_20000; "
      mariadb test -e "select count(*) from test_table"
      bash mcs_backup_manager.sh dbrm_restore --directory dbrm_backup_xxxxxxxxxxx
      mariadb test -e "select count(*) from test_table"
      

      Attachments

        Activity

          People

            leonid.fedorov Leonid Fedorov
            allen.herrera Allen Herrera
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.