innodb-utils 5.0.0

InnoDB file analysis toolkit
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

# inno verify

Verify structural integrity of a tablespace.

## Usage

```bash
# Basic verification
inno verify -f users.ibd

# Verbose output
inno verify -f users.ibd -v

# JSON output
inno verify -f users.ibd --json

# Verify with redo log
inno verify -f users.ibd --redo ib_logfile0

# Verify backup chain
inno verify --chain full.ibd incr1.ibd incr2.ibd
```

## Options

| Option | Description |
|--------|-------------|
| `-f, --file` | Path to InnoDB data file |
| `-v, --verbose` | Show per-page findings |
| `--json` | Output in JSON format |
| `--page-size` | Override page size |
| `--keyring` | Path to MySQL keyring file |
| `--redo` | Path to redo log file for LSN continuity check |
| `--chain` | Verify backup chain (accepts multiple files) |

## Structural Checks

| Check | Description |
|-------|-------------|
| PageNumberSequence | Page numbers match expected file positions |
| SpaceIdConsistency | All pages have consistent space IDs |
| LsnMonotonicity | LSNs are non-decreasing |
| BTreeLevelConsistency | B+Tree levels are valid |
| PageChainBounds | prev/next pointers within bounds |
| TrailerLsnMatch | Trailer LSN matches header LSN |

See the [Backup Verification](../guides/backup-verification.md) guide for detailed usage of `--chain` and `--redo`.