You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
29 lines
1.4 KiB
Markdown
29 lines
1.4 KiB
Markdown
# Restoring from a SQLite dump file
|
|
|
|
rqlite supports loading a node directly from a SQLite dump file. This is a fast and efficient manner to bootstrap a system from an existing SQLite database, or to restore from an existing [node backup](https://github.com/rqlite/rqlite/blob/master/doc/BACKUPS.md). An example restore is shown below.
|
|
|
|
## Example
|
|
The following example shows a trivial database being generated by `sqlite3`, dumped to a file, and then loaded into a rqlite node listening on localhost.
|
|
```bash
|
|
~ $ sqlite3 restore.sqlite
|
|
SQLite version 3.14.1 2016-08-11 18:53:32
|
|
Enter ".help" for usage hints.
|
|
sqlite> CREATE TABLE foo (id integer not null primary key, name text);
|
|
sqlite> INSERT INTO "foo" VALUES(1,'fiona');
|
|
sqlite>
|
|
~ $ echo '.dump' | sqlite3 restore.sqlite > restore.dump
|
|
~ $ curl -XPOST localhost:4001/db/load --data-binary @restore.dump
|
|
```
|
|
|
|
Let's connect to the node, and check that the data has been loaded correctly.
|
|
```bash
|
|
$ rqlite
|
|
127.0.0.1:4001> SELECT * FROM foo
|
|
+----+-------+
|
|
| id | name |
|
|
+----+-------+
|
|
| 1 | fiona |
|
|
+----+-------+
|
|
```
|
|
|
|
The behavior of the restore operation when data already exists on the node is undefined. Also, please note that SQLite dump files normally contain a command to disable Foreign Key constraints. If you wish to re-enable Foreign Key constraints after the load operation completes, check out [this documentation](https://github.com/rqlite/rqlite/blob/master/doc/FOREIGN_KEY_CONSTRAINTS.md). |