diff --git a/docs/apt-download-deb.md b/docs/apt-download-deb.md index 372068f7..c91c90ab 100644 --- a/docs/apt-download-deb.md +++ b/docs/apt-download-deb.md @@ -10,13 +10,13 @@ The following example downloads Percona XtraBackup {{release}} release package f 1. Use `wget` to download the `DEB` package: ```shell - wget https://downloads.percona.com/downloads/Percona-XtraBackup-{{vers}}/Percona-XtraBackup-{{release}}/binary/debian/jammy/x86_64/percona-xtrabackup-97_{{deb}}-1.jammy_amd64.deb + wget https://downloads.percona.com/downloads/Percona-XtraBackup-{{vers}}/Percona-XtraBackup-{{release}}/binary/debian/noble/x86_64/percona-xtrabackup-97_{{deb}}-1.noble_amd64.deb ``` 2. Install Percona XtraBackup by using `dpkg`: ```shell - sudo dpkg -i percona-xtrabackup-97_{{deb}}-1.jammy_amd64.deb + sudo dpkg -i percona-xtrabackup-97_{{deb}}-1.noble_amd64.deb ``` ## Common dependencies diff --git a/docs/apt-repo.md b/docs/apt-repo.md index 5a53b650..791bf1ff 100644 --- a/docs/apt-repo.md +++ b/docs/apt-repo.md @@ -20,14 +20,11 @@ Install Percona XtraBackup, like many other Percona products, with the `percona- ??? example "Expected output" ```{.text .no-copy} - Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB] - Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] - Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB] - Get:4 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [2458 kB] - ... - Building dependency tree... Done - Reading state information... Done - All packages are up to date. + Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease + Hit:2 http://security.ubuntu.com/ubuntu noble-security InRelease + Hit:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease + Hit:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease + Reading package lists... Done ``` 2. Install the `curl` download utility if it's not installed: @@ -97,14 +94,13 @@ Install Percona XtraBackup, like many other Percona products, with the `percona- ??? example "Expected output" ```{.text .no-copy} - Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB] - Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] - Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB] - Get:4 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [2458 kB] - ... - Building dependency tree... Done - Reading state information... Done - All packages are up to date. + Hit:1 http://repo.percona.com/prel/apt noble InRelease + Hit:2 http://repo.percona.com/telemetry/apt noble InRelease + Hit:3 http://archive.ubuntu.com/ubuntu noble InRelease + Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease + Hit:5 http://archive.ubuntu.com/ubuntu noble-updates InRelease + Hit:6 http://archive.ubuntu.com/ubuntu noble-backports InRelease + Reading package lists... Done ``` 6. Enable the specific percona-release product. @@ -116,18 +112,17 @@ Install Percona XtraBackup, like many other Percona products, with the `percona- ```{.text .no-copy} * Enabling the Percona Packaging Repository repository - Hit:1 http://repo.percona.com/pmm2-client/apt jammy InRelease - Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease - Hit:3 http://repo.percona.com/prel/apt jammy InRelease - Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease - Hit:5 http://archive.ubuntu.com/ubuntu jammy-updates InRelease - Get:6 http://repo.percona.com/{{pkg}}/apt jammy InRelease [12.8 kB] - Hit:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease - Hit:8 http://repo.percona.com/telemetry/apt jammy InRelease - Get:9 http://repo.percona.com/{{pkg}}/apt jammy/main Sources [855 B] - Get:10 http://repo.percona.com/{{pkg}}/apt jammy/main amd64 Packages [3547 B] - Fetched 17.2 kB in 4s (3958 B/s) - Reading package lists... Done + Hit:1 http://repo.percona.com/prel/apt noble InRelease + Get:2 http://repo.percona.com/pxb-97-lts/apt noble InRelease [12.8 kB] + Hit:3 http://repo.percona.com/telemetry/apt noble InRelease + Hit:4 http://archive.ubuntu.com/ubuntu noble InRelease + Hit:5 http://security.ubuntu.com/ubuntu noble-security InRelease + Hit:6 http://archive.ubuntu.com/ubuntu noble-updates InRelease + Hit:7 http://archive.ubuntu.com/ubuntu noble-backports InRelease + Get:8 http://repo.percona.com/pxb-97-lts/apt noble/main Sources [863 B] + Get:9 http://repo.percona.com/pxb-97-lts/apt noble/main amd64 Packages [3739 B] + Fetched 17.4 kB in 4s (3907 B/s) + Reading package lists... ``` 7. Install Percona XtraBackup. @@ -139,17 +134,22 @@ Install Percona XtraBackup, like many other Percona products, with the `percona- ??? example "Expected output" ```{.text .no-copy} - Reading package lists... Done - Building dependency tree... Done - Reading state information... Done + Reading package lists... + Building dependency tree... + Reading state information... The following additional packages will be installed: - libaio1 libcurl4-openssl-dev libdbd-mysql-perl libdbi-perl libev4 libgdbm-compat4 - libgdbm6 libmysqlclient21 libperl5.34 libpopt0 mysql-common netbase perl - perl-modules-5.34 rsync zstd + libaio1t64 libcurl4-openssl-dev libev4t64 libpopt0 lz4 rsync zstd + Suggested packages: + libcurl4-doc libidn-dev libkrb5-dev libldap2-dev librtmp-dev libssh2-1-dev + libssl-dev pkg-config zlib1g-dev openssh-client openssh-server python3 + python3-braceexpand + The following NEW packages will be installed: + libaio1t64 libcurl4-openssl-dev libev4t64 libpopt0 lz4 percona-xtrabackup-97 + rsync zstd + 0 upgraded, 8 newly installed, 0 to remove and 2 not upgraded. ... - Setting up libdbd-mysql-perl:amd64 (4.050-5ubuntu0.22.04.1) ...##############.......] - Setting up percona-xtrabackup-97 (9.7.1-rc1.jammy) ...#########################.....] - Processing triggers for libc-bin (2.35-0ubuntu3.8) ...###########################...] + Setting up percona-xtrabackup-97 ({{deb}}-1.noble) ... + Processing triggers for libc-bin (2.39-0ubuntu8.9) ... ``` 8. Verify the installation. @@ -161,7 +161,7 @@ Install Percona XtraBackup, like many other Percona products, with the `percona- ??? example "Expected output" ```{.text .no-copy} - xtrabackup version 9.7.1-rc1 based on MySQL server 9.7.1 Linux (x86_64) (revision id: da6e1abd) + xtrabackup version {{release}} based on MySQL server 9.7.1 Linux (x86_64) (revision id: b1c9c341) ``` 9. To decompress backups made using `LZ4` or `ZSTD` compression algorithm, install the corresponding package: diff --git a/docs/create-compressed-backup.md b/docs/create-compressed-backup.md index 9e1a2ac6..0c48452f 100644 --- a/docs/create-compressed-backup.md +++ b/docs/create-compressed-backup.md @@ -65,15 +65,12 @@ xtrabackup --backup --compress --compress-threads=4 \ ```{.text .no-copy} ... - 170223 13:00:38 [01] Compressing ./test/sbtest1.frm to /tmp/compressed/test/sbtest1.frm.qp - 170223 13:00:38 [01] ...done - 170223 13:00:38 [01] Compressing ./test/sbtest2.frm to /tmp/compressed/test/sbtest2.frm.qp - 170223 13:00:38 [01] ...done + 2026-10-13T17:24:45.357945-00:00 2 [Note] [MY-011825] [Xtrabackup] Compressing file with space_id 2 ./test/t1.ibd to /data/compressed/test/t1.ibd.zst + 2026-10-13T17:24:45.376746-00:00 2 [Note] [MY-011825] [Xtrabackup] Done: Compressing file with space_id 2 ./test/t1.ibd to /data/compressed/test/t1.ibd.zst ... - 170223 13:00:39 [00] Compressing xtrabackup_info - 170223 13:00:39 [00] ...done - xtrabackup: Transaction log of lsn (9291934) to (9291934) was copied. - 170223 13:00:39 completed OK! + 2026-10-13T17:24:46.558442-00:00 0 [Note] [MY-011825] [Xtrabackup] Compression ratio: 21.25x + 2026-10-13T17:24:47.563990-00:00 0 [Note] [MY-011825] [Xtrabackup] Transaction log of lsn (38309754) to (38309774) was copied. + 2026-10-13T17:24:47.796682-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` ## Next step diff --git a/docs/create-full-backup.md b/docs/create-full-backup.md index 1c073029..97243131 100644 --- a/docs/create-full-backup.md +++ b/docs/create-full-backup.md @@ -54,34 +54,26 @@ The following is an example of the output: ??? example "Expected output" ```{.text .no-copy} - 160906 10:19:17 Finished backing up non-InnoDB tables and files - 160906 10:19:17 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS... - xtrabackup: The latest check point (for incremental): '62988944' - xtrabackup: Stopping log copying thread. - .160906 10:19:18 >> log scanned up to (137343534) - 160906 10:19:18 Executing UNLOCK TABLES - 160906 10:19:18 All tables unlocked - 160906 10:19:18 Backup created in directory '/data/backups/' - 160906 10:19:18 [00] Writing backup-my.cnf - 160906 10:19:18 [00] ...done - 160906 10:19:18 [00] Writing xtrabackup_info - 160906 10:19:18 [00] ...done - xtrabackup: Transaction log of lsn (26970807) to (137343534) was copied. - 160906 10:19:18 completed OK! + ... + 2026-10-13T17:23:55.415104-00:00 0 [Note] [MY-011825] [Xtrabackup] Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS... + 2026-10-13T17:23:55.416681-00:00 0 [Note] [MY-011825] [Xtrabackup] The latest check point (for incremental): '36616867' + 2026-10-13T17:23:55.416693-00:00 0 [Note] [MY-011825] [Xtrabackup] Stopping log copying thread at LSN 36617774 + 2026-10-13T17:23:55.422875-00:00 0 [Note] [MY-011825] [Xtrabackup] Executing UNLOCK TABLES + 2026-10-13T17:23:55.423067-00:00 0 [Note] [MY-011825] [Xtrabackup] All tables unlocked + 2026-10-13T17:23:55.425280-00:00 0 [Note] [MY-011825] [Xtrabackup] Backup created in directory '/data/backups/' + 2026-10-13T17:23:55.425295-00:00 0 [Note] [MY-011825] [Xtrabackup] MySQL binlog position: filename 'binlog.000004', position '198', GTID of the last change 'd4193d59-c72a-11f1-90c5-46b9213cf448:1-5' + 2026-10-13T17:23:55.429852-00:00 0 [Note] [MY-011825] [Xtrabackup] Backup size: 98.60 MiB (103391867 bytes) + 2026-10-13T17:23:56.432866-00:00 0 [Note] [MY-011825] [Xtrabackup] Transaction log of lsn (36616867) to (36617784) was copied. + 2026-10-13T17:23:56.662202-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` -The process ends with the following statement; the -value of the `` depends on your system: - -```shell -xtrabackup: Transaction log of lsn () to () was copied. -``` +The last line of the output is `completed OK!`. Also check the exit code of the command: `0` means that the backup succeeded, any other value means that it failed. !!! note Log copying thread checks the transactional log every second to see if there were any new log records written that need to be copied, but there is a chance that the log copying thread might not be able to keep up with the amount of writes that go to the transactional logs, and will hit an error when the log records are overwritten before they could be read. -After the backup is finished, the target directory will contain files such as the following, assuming you have a single InnoDB table `test.tbl1` and you are using MySQL’s innodb_file_per_table option: +After the backup is finished, the target directory will contain files such as the following, for a server with a `test` database that contains two InnoDB tables: ```shell ls -lh /data/backups/ @@ -92,19 +84,24 @@ The result should look like this: ??? example "Expected output" ```{.text .no-copy} - total 182M - drwx------ 7 root root 4.0K Sep 6 10:19 . - drwxrwxrwt 11 root root 4.0K Sep 6 11:05 .. - -rw-r----- 1 root root 387 Sep 6 10:19 backup-my.cnf - -rw-r----- 1 root root 76M Sep 6 10:19 ibdata1 - drwx------ 2 root root 4.0K Sep 6 10:19 mysql - drwx------ 2 root root 4.0K Sep 6 10:19 performance_schema - drwx------ 2 root root 4.0K Sep 6 10:19 sbtest - drwx------ 2 root root 4.0K Sep 6 10:19 test - drwx------ 2 root root 4.0K Sep 6 10:19 world2 - -rw-r----- 1 root root 116 Sep 6 10:19 xtrabackup_checkpoints - -rw-r----- 1 root root 433 Sep 6 10:19 xtrabackup_info - -rw-r----- 1 root root 106M Sep 6 10:19 xtrabackup_logfile + total 76M + -rw-r----- 1 root root 452 Oct 13 17:23 backup-my.cnf + -rw-r----- 1 root root 198 Oct 13 17:23 binlog.000004 + -rw-r----- 1 root root 16 Oct 13 17:23 binlog.index + -rw-r----- 1 root root 5.7K Oct 13 17:23 ib_buffer_pool + -rw-r----- 1 root root 12M Oct 13 17:23 ibdata1 + drwxr-x--- 2 root root 4.0K Oct 13 17:23 mysql + -rw-r----- 1 root root 31M Oct 13 17:23 mysql.ibd + drwxr-x--- 2 root root 4.0K Oct 13 17:23 performance_schema + drwxr-x--- 2 root root 4.0K Oct 13 17:23 sys + drwxr-x--- 2 root root 4.0K Oct 13 17:23 test + -rw-r----- 1 root root 16M Oct 13 17:23 undo_001 + -rw-r----- 1 root root 16M Oct 13 17:23 undo_002 + -rw-r----- 1 root root 59 Oct 13 17:23 xtrabackup_binlog_info + -rw-r----- 1 root root 134 Oct 13 17:23 xtrabackup_checkpoints + -rw-r----- 1 root root 676 Oct 13 17:23 xtrabackup_info + -rw-r----- 1 root root 3.5K Oct 13 17:23 xtrabackup_logfile + -rw-r----- 1 root root 39 Oct 13 17:23 xtrabackup_tablespaces ``` The backup can take a long time, depending on how large the database is. It is safe to cancel at any time, because xtrabackup does not modify the database. diff --git a/docs/create-incremental-backup.md b/docs/create-incremental-backup.md index ba3f3a91..047ade12 100644 --- a/docs/create-incremental-backup.md +++ b/docs/create-incremental-backup.md @@ -38,10 +38,11 @@ content depending on your LSN nuber: ```{.text .no-copy} backup_type = full-backuped from_lsn = 0 - to_lsn = 1626007 - last_lsn = 1626007 - compact = 0 - recover_binlog_info = 1 + to_lsn = 36621132 + last_lsn = 36621132 + flushed_lsn = 36621122 + redo_memory = 0 + redo_frames = 0 ``` Now that you have a full backup, you can make an incremental backup based on it. Use the following command: @@ -61,11 +62,12 @@ content to the following: ```{.text .no-copy} backup_type = incremental - from_lsn = 1626007 - to_lsn = 4124244 - last_lsn = 4124244 - compact = 0 - recover_binlog_info = 1 + from_lsn = 36621132 + to_lsn = 37463526 + last_lsn = 37464185 + flushed_lsn = 37464150 + redo_memory = 0 + redo_frames = 0 ``` `from_lsn` is the starting LSN of the backup and for incremental it has to be the same as `to_lsn` (if it is the last checkpoint) of the previous/base backup. @@ -83,11 +85,12 @@ This folder also contains the `xtrabackup_checkpoints`: ```{.text .no-copy} backup_type = incremental - from_lsn = 4124244 - to_lsn = 6938371 - last_lsn = 7110572 - compact = 0 - recover_binlog_info = 1 + from_lsn = 37463526 + to_lsn = 38308481 + last_lsn = 38308481 + flushed_lsn = 38308446 + redo_memory = 0 + redo_frames = 0 ``` !!! note diff --git a/docs/encrypt-backups.md b/docs/encrypt-backups.md index 074c23fa..af26d7c4 100644 --- a/docs/encrypt-backups.md +++ b/docs/encrypt-backups.md @@ -87,5 +87,6 @@ You should check the last line of the output for a success message: ??? example "Expected output" ```{.text .no-copy} - 150318 11:08:13 xtrabackup: completed OK! + ... + 2026-10-13T17:25:10.030046-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` \ No newline at end of file diff --git a/docs/log-enhancements.md b/docs/log-enhancements.md index 516852d9..7b9ad356 100644 --- a/docs/log-enhancements.md +++ b/docs/log-enhancements.md @@ -60,22 +60,19 @@ or review the log to diagnose issues. ??? example "Expected output" ```{.text .no-copy} - 2022-03-22T19:15:36.142247+05:30 0 [Note] [MY-011825] [Xtrabackup] This target seems to be not prepared yet. - 2022-03-22T19:15:36.142792+05:30 0 [Note] [MY-013251] [InnoDB] Number of pools: 1 - 2022-03-22T19:15:36.149212+05:30 0 [Note] [MY-011825] [Xtrabackup] xtrabackup_logfile detected: size=8388608, start_lsn=(33311656) - 2022-03-22T19:15:36.149998+05:30 0 [Note] [MY-011825] [Xtrabackup] using the following InnoDB configuration for recovery: - 2022-03-22T19:15:36.150023+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_data_home_dir = . - 2022-03-22T19:15:36.150036+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_data_file_path = ibdata1:12M:autoextend - 2022-03-22T19:15:36.150078+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_log_group_home_dir = . - 2022-03-22T19:15:36.150095+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_log_files_in_group = 1 - 2022-03-22T19:15:36.150111+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_log_file_size = 8388608 - 2022-03-22T19:15:36.151667+05:30 0 [Note] [MY-011825] [Xtrabackup] inititialize_service_handles suceeded - 2022-03-22T19:15:36.151903+05:30 0 [Note] [MY-011825] [Xtrabackup] using the following InnoDB configuration for recovery: - 2022-03-22T19:15:36.151926+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_data_home_dir = . - 2022-03-22T19:15:36.151954+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_data_file_path = ibdata1:12M:autoextend - 2022-03-22T19:15:36.151976+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_log_group_home_dir = . - 2022-03-22T19:15:36.151991+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_log_files_in_group = 1 - 2022-03-22T19:15:36.152004+05:30 0 [Note] [MY-011825] [Xtrabackup] innodb_log_file_size = 8388608 - 2022-03-22T19:15:36.152021+05:30 0 [Note] [MY-011825] [Xtrabackup] Starting InnoDB instance for recovery. - 2022-03-22T19:15:36.152035+05:30 0 [Note] [MY-011825] [Xtrabackup] Using 104857600 bytes for buffer pool (set by --use-memory parameter) + 2026-10-13T17:24:07.116234-00:00 0 [Note] [MY-011825] [Xtrabackup] This target seems to be not prepared yet. + 2026-10-13T17:24:07.130815-00:00 0 [Note] [MY-011825] [Xtrabackup] xtrabackup_logfile detected: size=8388608, start_lsn=(36616867) + 2026-10-13T17:24:07.135585-00:00 0 [Note] [MY-011825] [Xtrabackup] using the following InnoDB configuration for recovery: + 2026-10-13T17:24:07.135620-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_data_home_dir = . + 2026-10-13T17:24:07.135625-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_data_file_path = ibdata1:12M:autoextend + 2026-10-13T17:24:07.136805-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_log_group_home_dir = . + 2026-10-13T17:24:07.136957-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_redo_log_capacity = 8388608 + 2026-10-13T17:24:07.138693-00:00 0 [Note] [MY-011825] [Xtrabackup] inititialize_service_handles suceeded + 2026-10-13T17:24:07.141331-00:00 0 [Note] [MY-011825] [Xtrabackup] using the following InnoDB configuration for recovery: + 2026-10-13T17:24:07.141346-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_data_home_dir = . + 2026-10-13T17:24:07.141349-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_data_file_path = ibdata1:12M:autoextend + 2026-10-13T17:24:07.141356-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_log_group_home_dir = . + 2026-10-13T17:24:07.141359-00:00 0 [Note] [MY-011825] [Xtrabackup] innodb_redo_log_capacity = 8388608 + 2026-10-13T17:24:07.141364-00:00 0 [Note] [MY-011825] [Xtrabackup] Starting InnoDB instance for recovery. + 2026-10-13T17:24:07.141369-00:00 0 [Note] [MY-011825] [Xtrabackup] Using 104857600 bytes for buffer pool (set by --use-memory parameter) ``` diff --git a/docs/prepare-compressed-backup.md b/docs/prepare-compressed-backup.md index dae0e07a..9f4f4a52 100644 --- a/docs/prepare-compressed-backup.md +++ b/docs/prepare-compressed-backup.md @@ -57,9 +57,9 @@ xtrabackup --prepare --target-dir=/data/compressed/ ??? example "Confirmation message" ```{.text .no-copy} - InnoDB: Starting shutdown... - InnoDB: Shutdown completed; log sequence number 9293846 - 170223 13:39:31 completed OK! + ... + 2026-10-13T17:25:02.032550-00:00 0 [Note] [MY-012980] [InnoDB] Shutdown completed; log sequence number 38309910 + 2026-10-13T17:25:02.039421-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` Now the files in `/data/compressed/` are ready to be used by the server. diff --git a/docs/prepare-full-backup.md b/docs/prepare-full-backup.md index 8397e38b..f0ec17aa 100644 --- a/docs/prepare-full-backup.md +++ b/docs/prepare-full-backup.md @@ -52,8 +52,9 @@ When this finishes, you should see an `InnoDB shutdown` with a message such as t ??? example "Expected output" ```{.text .no-copy} - InnoDB: Shutdown completed; log sequence number 137345046 - 160906 11:21:01 completed OK! + ... + 2026-10-13T17:24:08.568744-00:00 0 [Note] [MY-012980] [InnoDB] Shutdown completed; log sequence number 36618262 + 2026-10-13T17:24:08.576103-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` All following prepares will not change the already prepared data files, you’ll see that output says: diff --git a/docs/prepare-incremental-backup.md b/docs/prepare-incremental-backup.md index d45459a2..c3a58679 100644 --- a/docs/prepare-incremental-backup.md +++ b/docs/prepare-incremental-backup.md @@ -57,8 +57,9 @@ The log sequence number in the output should match the `to_lsn` value of the bas ??? example "Expected output" ```text - InnoDB: Shutdown completed; log sequence number 1626007 - 161011 12:41:04 completed OK! + ... + 2026-10-13T17:24:33.641122-00:00 0 [Note] [MY-012980] [InnoDB] Shutdown completed; log sequence number 36621142 + 2026-10-13T17:24:33.649010-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` !!! warning @@ -99,15 +100,15 @@ You should see output similar to the following: ??? example "Expected output" ```text - incremental backup from 1626007 is enabled. - xtrabackup: cd to /data/backups/base - xtrabackup: This target seems to be already prepared with --apply-log-only. - xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(4124244) + 2026-10-13T17:24:35.387201-00:00 0 [Note] [MY-011825] [Xtrabackup] incremental backup from 36621132 is enabled. + 2026-10-13T17:24:35.387458-00:00 0 [Note] [MY-011825] [Xtrabackup] cd to /data/backups/base/ + 2026-10-13T17:24:35.388208-00:00 0 [Note] [MY-011825] [Xtrabackup] This target seems to be already prepared with --apply-log-only. + 2026-10-13T17:24:35.412988-00:00 0 [Note] [MY-011825] [Xtrabackup] xtrabackup_logfile detected: size=8388608, start_lsn=(37463526) ... - xtrabackup: page size for /tmp/backups/inc1/ibdata1.delta is 16384 bytes - Applying /tmp/backups/inc1/ibdata1.delta to ./ibdata1... + 2026-10-13T17:24:35.668534-00:00 1 [Note] [MY-011825] [Xtrabackup] page size for /data/backups/inc1//ibdata1.delta is 16384 bytes + 2026-10-13T17:24:35.668646-00:00 1 [Note] [MY-011825] [Xtrabackup] Applying /data/backups/inc1//ibdata1.delta to ./ibdata1 ... - 161011 12:45:56 completed OK! + 2026-10-13T17:24:38.518719-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` The LSN should match the LSN from the first incremental backup. At this point, `/data/backups/base` contains the state of the database as of the first incremental backup. diff --git a/docs/quickstart-docker.md b/docs/quickstart-docker.md index 5f098c19..45595833 100644 --- a/docs/quickstart-docker.md +++ b/docs/quickstart-docker.md @@ -76,8 +76,7 @@ In this example of expected output, we provide the first and last section of the ```{.text .no-copy} - xtrabackup version {{release}} based on MySQL server 9.7.1 Linux (x86_64) (revision id: 3792f907) - 2024-10-07T13:55:51.255518-00:00 0 [Note] [MY-011825] [Xtrabackup] perl binary not found. Skipping the version check + xtrabackup version {{release}} based on MySQL server 9.7.1 Linux (x86_64) (revision id: b1c9c341) 2024-10-07T13:55:51.256080-00:00 0 [Note] [MY-011825] [Xtrabackup] Connecting to MySQL server host: localhost, user: root, password: set, port: not set, socket: not set 2024-10-07T13:55:51.270222-00:00 0 [Note] [MY-011825] [Xtrabackup] Using server version 9.7.1-1 2024-10-07T13:55:51.272839-00:00 0 [Note] [MY-011825] [Xtrabackup] Executing LOCK TABLES FOR BACKUP diff --git a/docs/quickstart-restore-back.md b/docs/quickstart-restore-back.md index e65e8235..bbaef69c 100644 --- a/docs/quickstart-restore-back.md +++ b/docs/quickstart-restore-back.md @@ -77,7 +77,7 @@ The following steps describe how to restore your backup to another Percona Serve ```{.text .no-copy} 2024-10-07T14:08:59.127166-00:00 0 [Note] [MY-011825] [Xtrabackup] recognized server arguments: --datadir=/var/lib/mysql/ 2024-10-07T14:08:59.128951-00:00 0 [Note] [MY-011825] [Xtrabackup] recognized client arguments: --copy-back=1 --target-dir=/backup_97 - xtrabackup version 9.7.1-1 based on MySQL server 9.7.1-1 Linux (x86_64) (revision id: 3792f907) + xtrabackup version {{release}} based on MySQL server 9.7.1 Linux (x86_64) (revision id: b1c9c341) 2024-10-07T14:08:59.129407-00:00 0 [Note] [MY-011825] [Xtrabackup] cd to /backup_97/ ... diff --git a/docs/working-with-binary-logs.md b/docs/working-with-binary-logs.md index 891382aa..d44136f1 100644 --- a/docs/working-with-binary-logs.md +++ b/docs/working-with-binary-logs.md @@ -9,10 +9,10 @@ You can find the binary log position corresponding to a backup after the backup ??? example "Expected output during the backup stage" ```{.text .no-copy} - 210715 14:14:59 Backup created in directory '/backup/' - MySQL binlog position: filename 'binlog.000002', position '156' - . . . - 210715 14:15:00 completed OK! + 2026-10-13T17:23:55.425280-00:00 0 [Note] [MY-011825] [Xtrabackup] Backup created in directory '/data/backups/' + 2026-10-13T17:23:55.425295-00:00 0 [Note] [MY-011825] [Xtrabackup] MySQL binlog position: filename 'binlog.000004', position '198', GTID of the last change 'd4193d59-c72a-11f1-90c5-46b9213cf448:1-5' + ... + 2026-10-13T17:23:56.662202-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK! ``` ## Point-in-time recovery diff --git a/docs/xtrabackup-option-reference.md b/docs/xtrabackup-option-reference.md index 4df0f99d..961fa2e6 100644 --- a/docs/xtrabackup-option-reference.md +++ b/docs/xtrabackup-option-reference.md @@ -835,7 +835,7 @@ When enabled, this options lets Percona XtraBackup register as a redo log consum Usage: `--remove-original` -This option removes `.qp`, `.xbcrypt` and `.qp.xbcrypt` files after decryption and decompression. +This option removes `.qp`, `.zst`, `.lz4`, and `.xbcrypt` files after decryption and decompression. ### rocksdb-datadir diff --git a/docs/yum-repo.md b/docs/yum-repo.md index 15cd9fba..478b7b74 100644 --- a/docs/yum-repo.md +++ b/docs/yum-repo.md @@ -61,16 +61,15 @@ To install Percona XtraBackup from Percona `yum` repository, do the following st ??? example "Expected output" ```{.text .no-copy} - PMM2 Client release/x86_64 YUM repository 17 kB/s | 7.1 kB 00:00 - Percona Release release/noarch YUM repository 5.3 kB/s | 2.0 kB 00:00 - Percona Packaging Repository release/x86_64 YUM 95 kB/s | 52 kB 00:00 - Percona Telemetry release/x86_64 YUM repository 4.3 kB/s | 1.7 kB 00:00 + Percona Release release/noarch YUM repository 16 kB/s | 2.8 kB 00:00 + Percona Packaging Repository release/x86_64 YUM 209 kB/s | 60 kB 00:00 + Percona Telemetry release/x86_64 YUM repository 25 kB/s | 5.4 kB 00:00 Dependencies resolved. ... - perl-subs-1.03-481.el9.noarch - perl-vars-1.05-481.el9.noarch - rsync-3.2.3-20.el9.x86_64 - zstd-1.5.1-2.el9.x86_64 + Installing: + percona-xtrabackup-97 x86_64 9.7.1-1.rc1.el9 pxb-97-lts-release-x86_64 41 M + ... + Complete! ``` 4. Verify the installation. @@ -82,7 +81,7 @@ To install Percona XtraBackup from Percona `yum` repository, do the following st ??? example "Expected output" ```{.text .no-copy} - xtrabackup version 9.7.0-1 based on MySQL server 9.7.1-1 Linux (x86_64) (revision id: da6e1abd) + xtrabackup version {{release}} based on MySQL server 9.7.1 Linux (x86_64) (revision id: b1c9c341) ``` 5. To decompress backups made using `LZ4` or `ZSTD` compression algorithm, install the corresponding package: