testjetco
- Total activity 49
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 11
Comments
Recent activity by testjetco Sort by recent activity-
For tables not sync issue in SIT, it was caused by the same reason. Some tables were defined as MyISAM at the very beginning. Then ppl performed transactions. Later we discovered that the engine...
-
I could decompress the backup files. Then I could use --prepare option to normalize the backup files. The file, backup-my.cnf, does exist inside the backup path after decompress. No need to crea...
-
From the URL: https://mariadb.com/kb/en/library/create-tablespace/ it said... "The CREATE TABLESPACE command is not supported in MariaDB. It is only used in MySQL Cluster and in MySQL InnoDB 5.7." ...
-
The issue is caused by db engine. Some tables were defined as MyISAM, which is not compatible with Galera clustering. After changing them to InnoDB, clustering sync works.
-
There is already a 2-node cluster in SIT, MariaDB version 10.3.10. Galera clustering was adopted. After installation and cluster up and running, we don't stop it. Yesterday, I have checked all th...
-
If I specify --all-databases, will all the tablespaces be backed up?
-
Install qpress to /usr/bin solved the decompress issue
-
When I tried to perform --decompress, I got the following error: # mariabackup --decompress --target-dir /tmp/backup/mariadb-backup-20181214213349mariabackup based on MariaDB server 10.3.10-MariaDB...
-
Here below are the backup files: [root@ekycdb1 mariadb-backup-20181214213349]# lltotal 276-rw-r-----. 1 root root 420 Dec 14 21:33 aria_log.00000001.qp-rw-r-----. 1 root root 129 Dec 14 21:33...
-
Not work. I have changed the file ownership for /tmp/backup/mariadb-backup-20181210182451/ to mysql:mysql Still 'cannot open backup-my.cnf for reading'. Anyone may help?