niota

To assist you in setting up the meta database from a backup there should be in ..\bin folder of tools.

Check your environment settings <here>.

If you start using niota on a new install with a blank MySQL Server there is not metadata database available which you could backup. Therefore we provide a backup of an initial database on the download page. Checkout download page and download current version of your metadata database.

We also provide some sample backups in the Windows accessory folders. Checkout your accessory folder for tools\dbrestore\database. Here you can find some .sql files that are ready to be restored with tool do_manage_metadb.

Once you have a database available on you MySQL Server you can backup it with this tool as well.

 
..

Script do_manage_metadb helps you to restore a metadata database from an existing backup. This tool expects some naming conventions to avoid any accidentially restore of data to a database. Read <doku> for further details on this requirements.

Command restore restores a given backup to an existing schema. Please take care, that the schema on which you restore is empty or that it is really, really, really the schema you want to overwrite. Once the restore is done, it's done!

If you need to create an empty schema on which you want to restore the backup please lookup <here>. Take care to create also the user on your MySQL DBMS which you set in then environment file

restore needs a user that has a least SUPER privilege, which is a global privilege. Grant this privilege to the user you use in your config or use a user that already has this privilege Usually root has all needed privileges.

run script do_manage_metadb with option restore

This script restores your

• given backup
  
• to the given schema
  

manage_metadb_restore.cmd

...\bin>do_manage_metadb niota_meta_c100 ***** restore

--- tool prints it settings 
-----------------------------------
DD.MM.YYYY 9:54:38,11 niota_meta_c100 is my universe
DD.MM.YYYY 9:54:38,11 Warpcore Manager 1.0 is my master
DD.MM.YYYY 9:54:38,12 admin_niota is my captain
DD.MM.YYYY 9:54:38,12 restore is my mission
DD.MM.YYYY 9:54:38,12 3367 is my warp tunnel
-----------------------------------

Mind the following messages below this block.

DD.MM.YYYY 9:57:03,67 ***INF: scriptfolder set due to option / "mysql" / "restore"

mysql: [Warning] Using a password on the command line interface can be insecure.
DD.MM.YYYY 9:57:07,50 ***INF: everything seems to be OK
DD.MM.YYYY 9:57:07,50 ***INF: finished restore
DD.MM.YYYY 9:57:07,51 ***INF: seems we are done!

Now check in you MySQL client tool, if all required objects are restored.