MySQL資料災難挽救之drop table
場景：開發人員對核心業務表誤刪除用了drop table語句，情況為無備份、未開啟BinLog特性。
思路：drop刪除之後只要資料不要重新整理增加把現在的磁碟記憶體覆蓋掉，可以透過undrop-for-innodb工具掃描磁碟讀取資料進行恢復資料。
說明：innodb_file_per_table=on，預設埠只能使用3306，且無法指定埠。因為透過掃描磁碟頁來找回資料的，為防止磁碟頁由於大量的IO操作，導致磁碟被重用無法找回資料。建議在誤操作之後剛磁碟掛載為只讀模式或直接停止業務，避免資料頁被重新整理。解析磁碟，大量資料情況下會出現資料丟失情況，酌情使用該工具恢復。
一、安裝undrop-for-innodb工具
shell> git clone git://github.com/twindb/undrop-for-innodb.git shell> yum install make gcc flex bison -y shell> cd undrop-for-innodb shell> make shell> gcc `$basedir/bin/mysql_config --cflags` `$basedir/bin/mysql_config --libs` -o sys_parser sys_parser.c 注：$basedir使用實際路徑替換
二、模擬測試資料
2.1 建立五萬條資料
mysql> create database test;
mysql> use test
Database changed
mysql> CREATE TABLE `test` (
-> `test_id` bigint NOT NULL AUTO_INCREMENT,
-> `first_name` varchar(45) NOT NULL,
-> `last_name` varchar(45) NOT NULL,
-> `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
-> PRIMARY KEY (`test_id`),
-> KEY `idx_test_last_name` (`last_name`)
-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
mysql> DELIMITER //
mysql> CREATE PROCEDURE mytest()
-> begin
-> declare i bigint;
-> set i=1;
-> while i<=10000 do
-> insert into test(first_name, last_name) values('zhang', 'san');
-> insert into test(first_name, last_name) values('zhan', 'san');
-> insert into test(first_name, last_name) values('zha', 'san');
-> insert into test(first_name, last_name) values('zh', 'san');
-> insert into test(first_name, last_name) values('z', 'san');
-> set i = i+1 ;
-> end while;
-> commit;
-> end
-> //
mysql> DELIMITER ;
mysql> call mytest();
mysql> select count(*) from test.test;
+----------+
| count(*) |
+----------+
| 50000 |
+----------+
2.2 刪除資料
mysql> DROP TABLE test.test;
三、恢復表結構
3.1 解析idata1檔案
由於DROP TABLE會直接從檔案系統刪除相關檔案，需要從系統表中恢復表結構。
shell> cd /root/undrop-for-innodb/ shell> /root/undrop-for-innodb/stream_parser -f /mysql/product/data/ibdata1 Opening file: /mysql/product/data/ibdata1 File information: ID of device containing file: 2051 inode number: 17714323 protection: 100640 (regular file) number of hard links: 1 user ID of owner: 1001 group ID of owner: 1001 device ID (if special file): 0 blocksize for filesystem I/O: 4096 number of blocks allocated: 409600 time of last access: 1637309362 Fri Nov 19 00:09:22 2021 time of last modification: 1637310349 Fri Nov 19 00:25:49 2021 time of last status change: 1637310349 Fri Nov 19 00:25:49 2021 total size, in bytes: 209715200 (200.000 MiB) Size to process: 209715200 (200.000 MiB) All workers finished in 0 sec shell> ll /root/undrop-for-innodb/pages-ibdata1/FIL_PAGE_INDEX/ total 1296 -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000001.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000002.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000003.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000004.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000005.page -rw-r--r-- 1 root root 16384 Nov 19 00:06 0000000000000011.page -rw-r--r-- 1 root root 16384 Nov 19 00:06 0000000000000012.page -rw-r--r-- 1 root root 16384 Nov 19 00:06 0000000000000013.page -rw-r--r-- 1 root root 16384 Nov 19 00:06 0000000000000014.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000015.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000016.page -rw-r--r-- 1 root root 16384 Nov 19 00:06 0000000000000017.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000032.page -rw-r--r-- 1 root root 32768 Nov 19 00:06 0000000000000033.page -rw-r--r-- 1 root root 655360 Nov 19 00:06 0000000000000045.page -rw-r--r-- 1 root root 278528 Nov 19 00:06 0000000000000046.page -rw-r--r-- 1 root root 16384 Nov 19 00:06 18446744069414584320.page 注： 0000000000000001.page SYS_TABLES 0000000000000002.page SYS_COLUMNS 0000000000000003.page SYS_INDEXES 0000000000000004.page SYS_FIELDS
3.2 抽取資料字典
shell> mkdir -p dumps/default shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000001.page -t dictionary/SYS_TABLES.sql > dumps/default/SYS_TABLES 2> dumps/default/SYS_TABLES.sql shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000002.page -t dictionary/SYS_COLUMNS.sql > dumps/default/SYS_COLUMNS 2> dumps/default/SYS_COLUMNS.sql shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000003.page -t dictionary/SYS_INDEXES.sql > dumps/default/SYS_INDEXES 2> dumps/default/SYS_INDEXES.sql shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000004.page -t dictionary/SYS_FIELDS.sql > dumps/default/SYS_FIELDS 2> dumps/default/SYS_FIELDS.sql
3.3 建立資料字典並載入到資料庫
shell> mysql -uroot -pHzmc321# mysql> CREATE DATABASE recover; shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dictionary/SYS_TABLES.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dumps/default/SYS_TABLES.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dictionary/SYS_COLUMNS.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dumps/default/SYS_COLUMNS.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dictionary/SYS_INDEXES.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dumps/default/SYS_INDEXES.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dictionary/SYS_FIELDS.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dumps/default/SYS_FIELDS.sql
3.4 獲取建表語句並建立格式檔案
shell> find / -name libmysqlclient.so.20 /mysql/app/lib/libmysqlclient.so.20 shell> ln -s /mysql/app/lib/libmysqlclient.so.20 /usr/local/lib/libmysqlclient.so.20 shell> vi /etc/ld.so.conf /usr/local/lib/ shell> /sbin/ldconfig -v shell> ./sys_parser -h 127.0.0.1 -u root -p Hzmc321# -d recover test/test CREATE TABLE `test`( `test_id` BIGINT NOT NULL, `first_name` VARCHAR(45) CHARACTER SET 'utf8' COLLATE 'utf8_general_ci' NOT NULL, `last_name` VARCHAR(45) CHARACTER SET 'utf8' COLLATE 'utf8_general_ci' NOT NULL, `last_update` TIMESTAMP NOT NULL, PRIMARY KEY (`test_id`) ) ENGINE=InnoDB; shell> vi /root/undrop-for-innodb/test.sql CREATE TABLE `test`( `test_id` BIGINT NOT NULL, `first_name` VARCHAR(45) CHARACTER SET 'utf8' COLLATE 'utf8_general_ci' NOT NULL, `last_name` VARCHAR(45) CHARACTER SET 'utf8' COLLATE 'utf8_general_ci' NOT NULL, `last_update` TIMESTAMP NOT NULL, PRIMARY KEY (`test_id`) ) ENGINE=InnoDB;
四、獲取表的table_id和索引頁
shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000001.page -t dictionary/SYS_TABLES.sql | grep test/test
SET FOREIGN_KEY_CHECKS=0;
LOAD DATA LOCAL INFILE '/root/undrop-for-innodb/dumps/default/SYS_TABLES' REPLACE INTO TABLE `SYS_TABLES` CHARACTER SET UTF8 FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_TABLES\t' (`NAME`, `ID`, `N_COLS`, `TYPE`, `MIX_ID`, `MIX_LEN`, `CLUSTER_NAME`, `SPACE`);
-- STATUS {"records_expected": 52, "records_dumped": 4, "records_lost": true} STATUS END
00000000D403 230000019102C8 SYS_TABLES "test/test" 42 4 33 0 80 "" 30
00000000D403 230000019102C8 SYS_TABLES "test/test" 42 4 33 0 80 "" 30
shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000003.page -t dictionary/SYS_INDEXES.sql | grep 42
SET FOREIGN_KEY_CHECKS=0;
LOAD DATA LOCAL INFILE '/root/undrop-for-innodb/dumps/default/SYS_INDEXES' REPLACE INTO TABLE `SYS_INDEXES` CHARACTER SET UTF8 FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_INDEXES\t' (`TABLE_ID`, `ID`, `NAME`, `N_FIELDS`, `TYPE`, `SPACE`, `PAGE_NO`);
-- STATUS {"records_expected": 64, "records_dumped": 20, "records_lost": true} STATUS END
0000000007A1 35000001890145 SYS_INDEXES 40 41 "PRIMARY" 1 3 24 4294967295
00000000D403 23000001910145 SYS_INDEXES 42 45 "PRIMARY" 1 3 30 4294967295
00000000D403 230000019101B7 SYS_INDEXES 42 46 "idx\_test\_last\_name" 1 0 30 4294967295
0000000007A1 35000001890145 SYS_INDEXES 40 41 "PRIMARY" 1 3 24 4294967295
00000000D403 23000001910145 SYS_INDEXES 42 45 "PRIMARY" 1 3 30 4294967295
00000000D403 230000019101B7 SYS_INDEXES 42 46 "idx\_test\_last\_name" 1 0 30 4294967295
shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000002.page -t dictionary/SYS_COLUMNS.sql | grep 42
SET FOREIGN_KEY_CHECKS=0;
LOAD DATA LOCAL INFILE '/root/undrop-for-innodb/dumps/default/SYS_COLUMNS' REPLACE INTO TABLE `SYS_COLUMNS` CHARACTER SET UTF8 FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_COLUMNS\t' (`TABLE_ID`, `POS`, `NAME`, `MTYPE`, `PRTYPE`, `LEN`, `PREC`);
-- STATUS {"records_expected": 274, "records_dumped": 34, "records_lost": true} STATUS END
00000000D403 230000019101F4 SYS_COLUMNS 42 0 "test\_id" 6 1288 8 0
00000000D403 2300000191025E SYS_COLUMNS 42 2 "last\_name" 12 2162959 135 0
00000000D403 23000001910229 SYS_COLUMNS 42 1 "first\_name" 12 2162959 135 0
00000000D403 23000001910293 SYS_COLUMNS 42 3 "last\_update" 3 525575 4 0
00000000D403 230000019101F4 SYS_COLUMNS 42 0 "test\_id" 6 1288 8 0
00000000D403 2300000191025E SYS_COLUMNS 42 2 "last\_name" 12 2162959 135 0
00000000D403 23000001910229 SYS_COLUMNS 42 1 "first\_name" 12 2162959 135 0
00000000D403 23000001910293 SYS_COLUMNS 42 3 "last\_update" 3 525575 4 0
shell> ./c_parser -5Df pages-ibdata1/FIL_PAGE_INDEX/0000000000000004.page -t dictionary/SYS_FIELDS.sql | grep '45\|46'
SET FOREIGN_KEY_CHECKS=0;
LOAD DATA LOCAL INFILE '/root/undrop-for-innodb/dumps/default/SYS_FIELDS' REPLACE INTO TABLE `SYS_FIELDS` CHARACTER SET UTF8 FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_FIELDS\t' (`INDEX_ID`, `POS`, `COL_NAME`);
-- STATUS {"records_expected": 92, "records_dumped": 4, "records_lost": true} STATUS END
-- Page id: 12, Format: REDUNDANT, Records list: Invalid, Expected records: (0 46)
00000000D403 23000001910110 SYS_FIELDS 45 0 "test\_id"
00000000D403 23000001910182 SYS_FIELDS 46 0 "last\_name"
-- Page id: 12, Format: REDUNDANT, Records list: Invalid, Expected records: (0 46)
00000000D403 23000001910110 SYS_FIELDS 45 0 "test\_id"
00000000D403 23000001910182 SYS_FIELDS 46 0 "last\_name"
五、恢復資料
shell> df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 895M 0 895M 0% /dev tmpfs 910M 0 910M 0% /dev/shm tmpfs 910M 11M 900M 2% /run tmpfs 910M 0 910M 0% /sys/fs/cgroup /dev/sda3 28G 13G 16G 45% / /dev/sda1 297M 165M 133M 56% /boot tmpfs 182M 12K 182M 1% /run/user/42 tmpfs 182M 0 182M 0% /run/user/0
5.1 解析datadir所在磁碟
shell> /root/undrop-for-innodb/stream_parser -f /dev/sda3 -s 1G -t 28G Disk cache: 1073741824 (1.000 GiB) Opening file: /dev/sda3 File information: ID of device containing file: 5 inode number: 10808 protection: 60660 (block device) number of hard links: 1 user ID of owner: 0 group ID of owner: 6 device ID (if special file): 2051 blocksize for filesystem I/O: 4096 number of blocks allocated: 0 time of last access: 1637309122 Fri Nov 19 00:05:22 2021 time of last modification: 1637309118 Fri Nov 19 00:05:18 2021 time of last status change: 1637309118 Fri Nov 19 00:05:18 2021 total size, in bytes: 0 (0.000 exp(+0)) Size to process: 30064771072 (28.000 GiB) Worker(0): 7.14% done. 2021-11-19 00:17:30 ETA(in 00:03:02). Processing speed: 146.283 MiB/sec Worker(0): 10.71% done. 2021-11-19 00:15:20 ETA(in 00:00:50). Processing speed: 512.000 MiB/sec Worker(0): 14.29% done. 2021-11-19 00:15:20 ETA(in 00:00:48). Processing speed: 512.000 MiB/sec Worker(0): 17.86% done. 2021-11-19 00:15:20 ETA(in 00:00:46). Processing speed: 512.000 MiB/sec Worker(0): 21.43% done. 2021-11-19 00:15:20 ETA(in 00:00:44). Processing speed: 512.000 MiB/sec Worker(0): 25.00% done. 2021-11-19 00:16:26 ETA(in 00:01:45). Processing speed: 204.800 MiB/sec Worker(0): 28.57% done. 2021-11-19 00:15:23 ETA(in 00:00:40). Processing speed: 511.992 MiB/sec Worker(0): 32.14% done. 2021-11-19 00:15:43 ETA(in 00:00:57). Processing speed: 341.328 MiB/sec Worker(0): 35.71% done. 2021-11-19 00:15:24 ETA(in 00:00:36). Processing speed: 512.000 MiB/sec Worker(0): 39.29% done. 2021-11-19 00:15:24 ETA(in 00:00:34). Processing speed: 512.000 MiB/sec Worker(0): 42.86% done. 2021-11-19 00:15:07 ETA(in 00:00:16). Processing speed: 1024.000 MiB/sec Worker(0): 46.43% done. 2021-11-19 00:15:39 ETA(in 00:00:45). Processing speed: 341.333 MiB/sec Worker(0): 50.00% done. 2021-11-19 00:16:24 ETA(in 00:01:24). Processing speed: 170.667 MiB/sec Worker(0): 53.57% done. 2021-11-19 00:16:10 ETA(in 00:01:05). Processing speed: 204.797 MiB/sec Worker(0): 57.14% done. 2021-11-19 00:16:36 ETA(in 00:01:24). Processing speed: 146.283 MiB/sec Worker(0): 60.71% done. 2021-11-19 00:16:24 ETA(in 00:01:06). Processing speed: 170.664 MiB/sec Worker(0): 64.29% done. 2021-11-19 00:15:29 ETA(in 00:00:10). Processing speed: 1023.984 MiB/sec Worker(0): 67.86% done. 2021-11-19 00:15:39 ETA(in 00:00:18). Processing speed: 512.000 MiB/sec Worker(0): 71.43% done. 2021-11-19 00:15:48 ETA(in 00:00:24). Processing speed: 341.333 MiB/sec Worker(0): 75.00% done. 2021-11-19 00:16:12 ETA(in 00:00:42). Processing speed: 170.667 MiB/sec Worker(0): 78.57% done. 2021-11-19 00:16:12 ETA(in 00:00:36). Processing speed: 170.664 MiB/sec Worker(0): 82.14% done. 2021-11-19 00:15:48 ETA(in 00:00:10). Processing speed: 511.992 MiB/sec Worker(0): 85.71% done. 2021-11-19 00:15:48 ETA(in 00:00:08). Processing speed: 512.000 MiB/sec Worker(0): 89.29% done. 2021-11-19 00:15:48 ETA(in 00:00:06). Processing speed: 512.000 MiB/sec Worker(0): 92.86% done. 2021-11-19 00:15:48 ETA(in 00:00:04). Processing speed: 512.000 MiB/sec Worker(0): 96.43% done. 2021-11-19 00:15:46 ETA(in 00:00:01). Processing speed: 1024.000 MiB/sec All workers finished in 93 sec
5.2 解析檢視聚集索引頁
shell> /root/undrop-for-innodb/c_parser -6f pages-sda3/FIL_PAGE_INDEX/0000000000000045.page -t test.sql > /root/45.log
SET FOREIGN_KEY_CHECKS=0;
LOAD DATA LOCAL INFILE '/root/undrop-for-innodb/dumps/default/test' REPLACE INTO TABLE `test` CHARACTER SET UTF8 FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'test\t' (`test_id`, `first_name`, `last_name`, `last_update`);
-- STATUS {"records_expected": 74030, "records_dumped": 74030, "records_lost": false} STATUS END
shell> more /root/45.log
-- Page id: 125, Format: COMPACT, Records list: Valid, Expected records: (395 395)
000000009DD0 C9000001460110 test 36538 "zha" "san" "2021-11-19 00:03:52"
000000009DD1 CA000001470110 test 36539 "zh" "san" "2021-11-19 00:03:52"
000000009DD2 CB000001480110 test 36540 "z" "san" "2021-11-19 00:03:52"
000000009DD3 CC000001490110 test 36541 "zhang" "san" "2021-11-19 00:03:52"
000000009DD4 CD0000014A0110 test 36542 "zhan" "san" "2021-11-19 00:03:52"
000000009DD5 CE0000014B0110 test 36543 "zha" "san" "2021-11-19 00:03:52"
000000009DD6 CF0000014C0110 test 36544 "zh" "san" "2021-11-19 00:03:52"
000000009DD7 D00000014D0110 test 36545 "z" "san" "2021-11-19 00:03:52"
000000009DD8 D10000014E0110 test 36546 "zhang" "san" "2021-11-19 00:03:52"
000000009DD9 D20000014F0110 test 36547 "zhan" "san" "2021-11-19 00:03:52"
000000009DDA D3000001500110 test 36548 "zha" "san" "2021-11-19 00:03:52"
000000009DDB D4000001510110 test 36549 "zh" "san" "2021-11-19 00:03:52"
000000009DDC D5000001520110 test 36550 "z" "san" "2021-11-19 00:03:52"
000000009DDD D6000001530110 test 36551 "zhang" "san" "2021-11-19 00:03:52"
000000009DDE D7000001540110 test 36552 "zhan" "san" "2021-11-19 00:03:52"
000000009DDF D8000001550110 test 36553 "zha" "san" "2021-11-19 00:03:52"
000000009DE0 D9000001560110 test 36554 "zh" "san" "2021-11-19 00:03:52"
000000009DE1 DA000001570110 test 36555 "z" "san" "2021-11-19 00:03:52"
000000009DE2 DB000001580110 test 36556 "zhang" "san" "2021-11-19 00:03:52"
000000009DE3 DC000001590110 test 36557 "zhan" "san" "2021-11-19 00:03:52"
000000009DE4 DD0000015A0110 test 36558 "zha" "san" "2021-11-19 00:03:52"
000000009DE5 DE0000015B0110 test 36559 "zh" "san" "2021-11-19 00:03:52"
000000009DE6 DF0000015C0110 test 36560 "z" "san" "2021-11-19 00:03:52"
000000009DE7 E00000015D0110 test 36561 "zhang" "san" "2021-11-19 00:03:52"
000000009DE8 E10000015E0110 test 36562 "zhan" "san" "2021-11-19 00:03:52"
000000009DE9 E20000015F0110 test 36563 "zha" "san" "2021-11-19 00:03:52"
000000009DEA E3000001600110 test 36564 "zh" "san" "2021-11-19 00:03:52"
000000009DEB E4000001610110 test 36565 "z" "san" "2021-11-19 00:03:52"
000000009DEC E5000001620110 test 36566 "zhang" "san" "2021-11-19 00:03:52"
000000009DED E6000001630110 test 36567 "zhan" "san" "2021-11-19 00:03:52"
000000009DEE E7000001640110 test 36568 "zha" "san" "2021-11-19 00:03:52"
000000009DEF E8000001650110 test 36569 "zh" "san" "2021-11-19 00:03:52"
000000009DF0 E9000001660110 test 36570 "z" "san" "2021-11-19 00:03:52"
--More--(0%)
[1]+ Stopped more /root/45.log
5.3 解析並恢復至資料庫
shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/test.sql shell> /root/undrop-for-innodb/c_parser -6f pages-sda3/FIL_PAGE_INDEX/0000000000000045.page -t test.sql > dumps/default/test 2> dumps/default/test.sql shell> mysql -uroot -pHzmc321# recover < /root/undrop-for-innodb/dumps/default/test.sql mysql> select count(*) from recover.test; +----------+ | count(*) | +----------+ | 17808 | +----------+ 1 row in set (0.00 sec)
恢復資料，有丟失資料，在非必要情況下，不建議選擇該方式恢復資料
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/30310891/viewspace-2843848/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- MySQL資料災難挽救之truncate tableMySql
- MySQL資料災難挽救之Delete\UpdateMySqldelete
- oracle資料庫災難挽救應急方案之DDL誤操作恢復（drop）Oracle資料庫
- MySQL資料災難挽救之ibdata檔案誤刪恢復MySql
- oracle資料庫災難挽救應急方案之DML誤操作恢復Oracle資料庫
- oracle資料庫災難挽救應急方案之DDL誤操作恢復（truncate）Oracle資料庫
- drop apply INSTANTIATION for one tableAPP
- create table，show tables，describe table，DROP TABLE，ALTER TABLE ，怎麼使用？
- alter table drop unused columns checkpoint
- 6、MySQL刪除資料庫（DROP DATABASE語句）MySql資料庫Database
- 直接登入資料庫使用drop table tablename;會是什麼情況？資料庫
- 深入解析 oracle drop table內部原理Oracle
- MySQL Shell import_table資料匯入MySqlImport
- 【資料庫資料恢復】ORACLE常見資料災難&資料恢復可能性資料庫資料恢復Oracle
- mysql之 OPTIMIZE TABLE整理碎片MySql
- MySQL：mysqldump 匯出資料異常重啟及drop棧幀MySql
- 解決資料災難需要回答的十個問題
- 基於UNIX系統，邏輯故障的資料災難解讀
- 細數基於ORACLE 資料庫環境的常見資料災難解決方式Oracle資料庫
- Veeam助力TrendMicro解決資料保護和災難恢復挑戰
- [20181203]drop table後如何獲得表結構.txt
- 資料庫的災備資料庫
- oracle drop table purge無備份bbed恢復(3/3)Oracle
- oracle drop table purge無備份bbed恢復(1/3)Oracle
- oracle drop table purge無備份bbed恢復(2/3)Oracle
- MySQL資料庫之索引MySql資料庫索引
- MySQL 8.0 之資料字典MySql
- MySQL之json資料操作MySqlJSON
- 伺服器資料恢復-UNIX類檔案系統資料災難的資料恢復可能性分析伺服器資料恢復
- HP-lefthand底層結構詳解及儲存災難資料恢復資料恢復
- MySQL預設資料庫之mysql庫MySql資料庫
- 資料庫：drop、truncate、delete的區別資料庫delete
- VMware Live Site Recovery 9.0 - 資料中心災難恢復 (DR)
- VMware Site Recovery Manager 9.0 - 資料中心災難恢復 (DR)
- VMware Live Site Recovery 9.0.1 - 資料中心災難恢復 (DR)
- IT系統災難恢復基本指南
- MySQL5.7下面，誤操作導致的drop table db1.tb1; 的恢復方法：MySql
- Python之 操作 MySQL 資料庫PythonMySql資料庫