subject: The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly: * It includes [print this page] The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly: * It includes
The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly:
It includes the InnoDB page checksum calculations, so it can verify that the pages it copies are not corrupt from InnoDB's point of view.
It looks at the data it copies in multiples of 4kb, from 16kB down to 4kB, to see if they are InnoDB pages. In this way it detects any InnoDB data page in the 4-16kB range automatically.
If InnoDB's checksum algorithm reports that a page is corrupt, it tries to read it again; it retries 9 times.
If possible, it uses the following two POSIX fadvise() calls to optimize operating system cache usage, in the same fashion as xtrabackup:
The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly:
It includes the InnoDB page checksum calculations, so it can verify that the pages it copies are not corrupt from InnoDB's point of view.
It looks at the data it copies in multiples of 4kb, from 16kB down to 4kB, to see if they are InnoDB pages. In this way it detects any InnoDB data page in the 4-16kB range automatically.
If InnoDB's checksum algorithm reports that a page is corrupt, it tries to read it again; it retries 9 times.
If possible, it uses the following two POSIX fadvise() calls to optimize operating system cache usage, in the same fashion as xtrabackup:
The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly:
It includes the InnoDB page checksum calculations, so it can verify that the pages it copies are not corrupt from InnoDB's point of view.
It looks at the data it copies in multiples of 4kb, from 16kB down to 4kB, to see if they are InnoDB pages. In this way it detects any InnoDB data page in the 4-16kB range automatically.
If InnoDB's checksum algorithm reports that a page is corrupt, it tries to read it again; it retries 9 times.
If possible, it uses the following two POSIX fadvise() calls to optimize operating system cache usage, in the same fashion as xtrabackup:
The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly:
It includes the InnoDB page checksum calculations, so it can verify that the pages it copies are not corrupt from InnoDB's point of view.
It looks at the data it copies in multiples of 4kb, from 16kB down to 4kB, to see if they are InnoDB pages. In this way it detects any InnoDB data page in the 4-16kB range automatically.
If InnoDB's checksum algorithm reports that a page is corrupt, it tries to read it again; it retries 9 times.
If possible, it uses the following two POSIX fadvise() calls to optimize operating system cache usage, in the same fashion as xtrabackup:
The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly:
It includes the InnoDB page checksum calculations, so it can verify that the pages it copies are not corrupt from InnoDB's point of view.
It looks at the data it copies in multiples of 4kb, from 16kB down to 4kB, to see if they are InnoDB pages. In this way it detects any InnoDB data page in the 4-16kB range automatically.
If InnoDB's checksum algorithm reports that a page is corrupt, it tries to read it again; it retries 9 times.
If possible, it uses the following two POSIX fadvise() calls to optimize operating system cache usage, in the same fashion as xtrabackup:
The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly:
It includes the InnoDB page checksum calculations, so it can verify that the pages it copies are not corrupt from InnoDB's point of view.
It looks at the data it copies in multiples of 4kb, from 16kB down to 4kB, to see if they are InnoDB pages. In this way it detects any InnoDB data page in the 4-16kB range automatically.
If InnoDB's checksum algorithm reports that a page is corrupt, it tries to read it again; it retries 9 times.
If possible, it uses the following two POSIX fadvise() calls to optimize operating system cache usage, in the same fashion as xtrabackup:
The tar4ibd binary is a specially patched version of tar that understands how to handle InnoDB/XtraDB data files correctly:
It includes the InnoDB page checksum calculations, so it can verify that the pages it copies are not corrupt from InnoDB's point of view.
It looks at the data it copies in multiples of 4kb, from 16kB down to 4kB, to see if they are InnoDB pages. In this way it detects any InnoDB data page in the 4-16kB range automatically.
If InnoDB's checksum algorithm reports that a page is corrupt, it tries to read it again; it retries 9 times.
If possible, it uses the following two POSIX fadvise() calls to optimize operating system cache usage, in the same fashion as xtrabackup:
