6. ClustrixDB 备份恢复

ClustrixDB备份恢复：

 

一、传统MySQL的备份/恢复

shell> mysqldump -u user -h clustrix host --single-transaction --master-data=2 --all-databases > mydumpfile.dump

二、ClustrixDB的备份/恢复

备份testdb下面所有表到/tmp/backup目录中

MySQL [testdb]> select count(*) from userinfo_uuid;
+----------+
| count(*) |
+----------+
| 10000 |
+----------+
1 row in set (0.01 sec)

MySQL [(none)]>  backup testdb.* to "sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/backup" ;

Query OK, 0 rows affected (1.92 sec)

恢复：

MySQL [testdb]> drop database testdb;
Query OK, 0 rows affected (0.01 sec)

MySQL [(none)]> RESTORE * FROM "sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/backup" REPLICAS = 1;
Query OK, 0 rows affected (59.74 sec)
MySQL [(none)]> RESTORE * FROM "sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/backup" REPLICAS = 2;
Query OK, 0 rows affected (1 min 52.63 sec)

MySQL [testdb]> use testdb; show tables;
+------------------+
| Tables_in_testdb |
+------------------+
| userinfo_uuid |
+------------------+
1 row in set (0.02 sec)

MySQL [testdb]> select count(*) from userinfo_uuid;
+----------+
| count(*) |
+----------+
| 10000 |
+----------+
1 row in set (0.01 sec)

提高备份性能，默认备份进程一次备份一张表

MySQL [(none)]> show variables like 'bsackup_backup_concurrency';
+---------------------------+-------+
| Variable_name | Value |
+---------------------------+-------+
| backup_backup_concurrency | 1 |
+---------------------------+-------+
1 row in set (0.00 sec)

MySQL [(none)]> backup scloud.*,test.* to "sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/backup" ;
Query OK, 0 rows affected (2.12 sec)

MySQL [(none)]> \! sudo rm -rf /tmp/backup
MySQL [(none)]> set global backup_backup_concurrency=2;
Query OK, 0 rows affected (0.01 sec)

MySQL [(none)]> backup scloud.*,test.* to "sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/backup" ;
Query OK, 0 rows affected (1.51 sec)

查看备份文件信息：

MySQL [system]> SELECT * from system.backups where source="sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/"\G
*************************** 1. row ***************************
source: sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/
backup: backup
cluster_name: cld32d48dc6ff9c79d
version: clustrix-9.2
status: COMPLETED
start_time: 2019-11-28 03:23:41.084376
completed_time: 2019-11-28 03:23:42.581939
bytes: 179548772
1 row in set (1.94 sec)

查看备份文件中表信息

MySQL [system]> SELECT * from system.backup_tables where source="sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/"\G;
*************************** 1. row ***************************
source: sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/
backup: backup
db: scloud
table: sbtest1
bytes: 179545464
*************************** 2. row ***************************
source: sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/
backup: backup
db: test
table: foo
bytes: 68
*************************** 3. row ***************************
source: sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/
backup: backup
db: test
table: sb2
bytes: 1608
*************************** 4. row ***************************
source: sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/
backup: backup
db: test
table: sbtest1
bytes: 1584
*************************** 5. row ***************************
source: sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/
backup: backup
db: test
table: t1
bytes: 26
*************************** 6. row ***************************
source: sftp://scloudusr:Scloud201!@10.1.3.88:2022/tmp/
backup: backup
db: test
table: t2
bytes: 22
6 rows in set (1.95 sec)

影响备份恢复的global参数：

Name	Description	Default Value
backup_backup_concurrency	The number of tables that can be backed up simultaneously.	1
backup_restore_concurrency	The maximum number of slices restored concurrently on each node.	16
backup_write_compression_level	Compression level from 1 (fastest) to 9 (best compression)	6

备份/恢复的错误列表

Backup

Error	Meaning
Bad Parameter.:"Backup..." is invalid Bad parameter.: *.* is repeated in the list Bad parameter.: DB "..." is included multiple times Bad parameter.: "..." is included multiple times Bad parameter.: nothing to back up! Unrecognized backup url scheme: ... syntax error: ...	Something is wrong with the BACKUP statement, please double check
Generic Error: no user DB found Bad parameter.: Hidden database '...' cannot be backed up No such database: '...' Not found: Object "..." does not exist Not found: There are more than one "..." Backup only supported for TABLES right now: ...	Trying to backup something that cannot be backed-up, or doesn't exist
Representation is unavailable: ... Generic Backup Error: Couldn't find baserep for ... Generic Backup Error: Couldn't find columns for ...	Trying to backup something currently unavailable
Bad backup URL: ...	Unable to parse URL or connect to FTP server
Backup already exists in create: ...	There is already a backup at that location
Upload of slice was truncated on remote host: ...	File written to backup was shorter than it should have been
EXCLUDING *.* is invalid	Would backup nothing
“...” is repeated in the EXCLUDING clause	Object is excluded more than once

Restore

Error	Meaning
Bad parameter.: "RESTORE ..." is invalid Bad parameter.: Global wildcard *.* is used together with other targets Bad parameter.: DB "..." already exists on server or in the target list Bad parameter.: Target "..." already exists Bad parameter.: "..." is repeated in the target list Generic Backup Error: newdbnames array length must be same as dbnames Unrecognized backup url scheme: ... syntax error: ...	Something is wrong with the RESTORE statement
Bad backup URL: ...	Unable to parse URL or connect to FTP server
Unable to open backup for url: ...	Cannot open backup directory on FTP server
Backup not available for restore: ...	This backup did not complete successfully
DB not found in backup: ...	Trying to restore something that is not in the backup
Object not found in backup: ...
DB already exists in the target location: ... Generic Backup Error: could not parse create statement: ...	Cannot create object
Unable to validate CREATE statement: ...	Created object does not match backed-up object
Generic Backup Error: could not parse column types from backup table "..." Column type mismatch during restore: ... Hash layout mismatch during restore: ...
Unable to locate stored CRC of file: ... Backup CRC Mismatch: ... Unable to locate uncompressed length of file: ...	Backup is corrupt
Restore truncated by incomplete read: ...	Read too little data for a row
“...” is repeated in the EXCLUDING clause	Object is excluded more than once
Relation not found: While restoring object db_name.obj_name...	The object noted references another that does not exist. The missing object is shown in parenthesis. For example, this error occurs if a table was excluded from the backup, but the associated views or triggers were not.

Zlib errors

Error	Meaning
Internal Error: Unexpected buffering stop	Internal buffering error
Internal Error: Unexpected stop

FTP Errors

Error	Meaning
File not found
FTP Socket Closed
Invalid argument to API	Bad internal usage of our FTP interface
Socket timeout while waiting for server response
Unexpected error response from server
Unexpected response to PASS command
Unexpected response to USER command
Unexpected temporary error response from server

SFTP Errors

Error	Meaning
Error	Meaning
A file that isn’t a directory was specified when a directory is required
An attempt was made to modify something on a read-only file system
Bad file descriptor
Broken pipe	There is no process reading from the other end of a pipe
Directory not empty, where an empty directory was expected	Typically, this error occurs when you are trying to delete a directory
File exists	An existing file was specified in a context where it only makes sense to specify a new file
No space left on device	Write operation on a file failed because the disk is full
No such device or address	The system tried to use the device represented by a file you specified, and it couldn’t find the device
No such file or directory
Permission denied
SSH authentication failed
SSH timeout	The SSH server closed the connection due to a timeout
The socket is not connected to anything	You get this error when you try to transmit data over a socket, without first specifying a destination for the data
Too many levels of symbolic links were encountered in looking up a file name	This often indicates a cycle of symbolic links
Unexpected SSH error	Something happened during the SSH protocol that we didn't expect