【已解答】MySQL数据库备份恢复时缺少几张表

为了能快速了解并处理您的问题，请提供以下基础信息：

面板、插件版本：免费版 8.0.2

系统版本： CentOS 7.8.2003 x86_64(Py3.7.8)

问题描述：备份MySQL数据库后，再次恢复时缺少5张表，已经试过将数据导入新建的数据库，也是缺少这几张表，在导入的时候都没有提示错误，导入完毕后还提示导入成功。

相关截图（日志、错误）：查看备份的sql文件内是有这5张表的，以及对应的数据。导入时缺少以下的表，表结构如下

--
-- Table structure for table `qrtz_blob_triggers`
--
DROP TABLE IF EXISTS `qrtz_blob_triggers`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `qrtz_blob_triggers` (
`sched_name` varchar(120) COLLATE utf8mb4_bin NOT NULL,
`trigger_name` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`trigger_group` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`blob_data` blob,
PRIMARY KEY (`sched_name`,`trigger_name`,`trigger_group`) USING BTREE,
CONSTRAINT `qrtz_blob_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=DYNAMIC;
/*!40101 SET character_set_client = @saved_cs_client */;

复制代码

--
-- Table structure for table `qrtz_cron_triggers`
--
DROP TABLE IF EXISTS `qrtz_cron_triggers`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `qrtz_cron_triggers` (
`sched_name` varchar(120) COLLATE utf8mb4_bin NOT NULL,
`trigger_name` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`trigger_group` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`cron_expression` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`time_zone_id` varchar(80) COLLATE utf8mb4_bin DEFAULT NULL,
PRIMARY KEY (`sched_name`,`trigger_name`,`trigger_group`) USING BTREE,
CONSTRAINT `qrtz_cron_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=DYNAMIC;
/*!40101 SET character_set_client = @saved_cs_client */;

复制代码

--
-- Table structure for table `qrtz_simple_triggers`
--
DROP TABLE IF EXISTS `qrtz_simple_triggers`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `qrtz_simple_triggers` (
`sched_name` varchar(120) COLLATE utf8mb4_bin NOT NULL,
`trigger_name` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`trigger_group` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`repeat_count` bigint(7) NOT NULL,
`repeat_interval` bigint(12) NOT NULL,
`times_triggered` bigint(10) NOT NULL,
PRIMARY KEY (`sched_name`,`trigger_name`,`trigger_group`) USING BTREE,
CONSTRAINT `qrtz_simple_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=DYNAMIC;
/*!40101 SET character_set_client = @saved_cs_client */;

复制代码

--
-- Table structure for table `qrtz_simprop_triggers`
--
DROP TABLE IF EXISTS `qrtz_simprop_triggers`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `qrtz_simprop_triggers` (
`sched_name` varchar(120) COLLATE utf8mb4_bin NOT NULL,
`trigger_name` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`trigger_group` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`str_prop_1` varchar(512) COLLATE utf8mb4_bin DEFAULT NULL,
`str_prop_2` varchar(512) COLLATE utf8mb4_bin DEFAULT NULL,
`str_prop_3` varchar(512) COLLATE utf8mb4_bin DEFAULT NULL,
`int_prop_1` int(11) DEFAULT NULL,
`int_prop_2` int(11) DEFAULT NULL,
`long_prop_1` bigint(20) DEFAULT NULL,
`long_prop_2` bigint(20) DEFAULT NULL,
`dec_prop_1` decimal(13,4) DEFAULT NULL,
`dec_prop_2` decimal(13,4) DEFAULT NULL,
`bool_prop_1` varchar(1) COLLATE utf8mb4_bin DEFAULT NULL,
`bool_prop_2` varchar(1) COLLATE utf8mb4_bin DEFAULT NULL,
PRIMARY KEY (`sched_name`,`trigger_name`,`trigger_group`) USING BTREE,
CONSTRAINT `qrtz_simprop_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=DYNAMIC;
/*!40101 SET character_set_client = @saved_cs_client */;

复制代码

--
-- Table structure for table `qrtz_triggers`
--
DROP TABLE IF EXISTS `qrtz_triggers`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `qrtz_triggers` (
`sched_name` varchar(120) COLLATE utf8mb4_bin NOT NULL,
`trigger_name` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`trigger_group` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`job_name` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`job_group` varchar(200) COLLATE utf8mb4_bin NOT NULL,
`description` varchar(250) COLLATE utf8mb4_bin DEFAULT NULL,
`next_fire_time` bigint(13) DEFAULT NULL,
`prev_fire_time` bigint(13) DEFAULT NULL,
`priority` int(11) DEFAULT NULL,
`trigger_state` varchar(16) COLLATE utf8mb4_bin NOT NULL,
`trigger_type` varchar(8) COLLATE utf8mb4_bin NOT NULL,
`start_time` bigint(13) NOT NULL,
`end_time` bigint(13) DEFAULT NULL,
`calendar_name` varchar(200) COLLATE utf8mb4_bin DEFAULT NULL,
`misfire_instr` smallint(2) DEFAULT NULL,
`job_data` blob,
PRIMARY KEY (`sched_name`,`trigger_name`,`trigger_group`) USING BTREE,
KEY `sched_name` (`sched_name`,`job_name`,`job_group`) USING BTREE,
CONSTRAINT `qrtz_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `job_name`, `job_group`) REFERENCES `qrtz_job_details` (`sched_name`, `job_name`, `job_group`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=DYNAMIC;
/*!40101 SET character_set_client = @saved_cs_client */;

复制代码

谢花郎 · 发表于 2023-9-5 10:05:38

您好，面板内导入数据备份是不会校验您数据是否能否正常导入的，如果无法正常导入，您可以通过PHPmyadmin或者命令行导入看下是否有提示错误，请您根据MySQL导入时提示返回的错误码进行一个排查语句或表结构。