> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/server/server-usage/backup-and-restore/mariadb-backup/point-in-time-recovery-pitr-mariadb-backup.md).

# Point-In-Time Recovery (PITR, mariadb-backup)

Recovering from a backup can restore the data directory at a specific point in time, but it does not restore the binary log. In a point-in-time recovery, start by restoring the data directory from a full or incremental backup, then use the [mysqlbinlog](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog/mariadb-binlog-mysqlbinlog.md) utility to restore the binary log data to a specific point in time.

{% hint style="warning" %}
Run the following commands as root unless indicated otherwise.
{% endhint %}

{% stepper %}
{% step %}
**Find the binary log position to restore to.**

When MariaDB Backup runs on a MariaDB Server with binary logs enabled (which is a prerequisite for PITR), it stores binary log information in the `mariadb_backup_binlog_info` (or `xtrabackup_binlog_info` in [older releases](/docs/server/server-usage/backup-and-restore/mariadb-backup/files-created-by-mariadb-backup.md)) file. Consult this file to find the name of the binary log position to use. In the following example, the log position is 321:

```bash
cat /data/backups/full/mariadb_backup_binlog_info

mariadb-node4.00001     321
```

{% endstep %}

{% step %}
**Configure a new data directory.**

Update the configuration file (for instance, `my.cnf`) to use a new data directory.

```ini
[mysqld]
datadir=/var/lib/mysql_new
```

{% endstep %}

{% step %}
**Restore the backup.**

Restore from the backup [as explained here](/docs/server/server-usage/backup-and-restore/mariadb-backup/full-backup-and-restore-with-mariadb-backup.md).
{% endstep %}

{% step %}
**Start the database server.**

Start MariaDB Server.

```bash
systemctl start mariadb
```

{% endstep %}

{% step %}
**Create a script using mysqlbinlog.**

Use the mysqlbinlog utility to create an SQL script, using the binary log file in the *old* data directory, the start position in the `xtrabackup_binlog_info` file, and the date and time you want to restore to. Issue the following command *as a regular user*:

```bash
$ mysqlbinlog --start-position=321 \
      --stop-datetime="2019-06-28 12:00:00" \
      /var/lib/mysql/mariadb-node4.00001 \
      > mariadb-binlog.sql
```

{% endstep %}

{% step %}
**Run the script.**

In the *new* data directory, run the script created in the previous step:

```bash
$ mariadb < mariadb-binlog.sql
```

{% endstep %}
{% endstepper %}

## See Also

* [Point-In-Time Recovery (InnoDB log archiving)](/docs/server/server-usage/backup-and-restore/innodb-log-archive-pitr.md) — an alternative PITR procedure that replays archived InnoDB write-ahead logs instead of binary logs. Available from MariaDB 13.0.

{% hint style="warning" %}
[`mariadb-backup`](/docs/server/server-usage/backup-and-restore/mariadb-backup.md) does not support the [`innodb_log_archive`](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#innodb_log_archive)`=ON` log format and fails when the server is running with `innodb_log_archive=ON`. Use the [InnoDB log archiving PITR](/docs/server/server-usage/backup-and-restore/innodb-log-archive-pitr.md) procedure instead in that configuration.
{% endhint %}