Repository navigation
Replies: 1 comment
|
No, What it saves is a backend database snapshot from the member. That file contains the committed key-value state at the snapshot revision, so During restore, etcd writes that database into a new data directory and creates fresh WAL and snapshot metadata there. So for this restore path, you do not need a separate copy of the old WAL files. The snapshot only covers the state at the snapshot point. Writes after the snapshot are not included. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Does
snapshot save backup.dbcommit the *.wal files to backup.db, forming a complete database file so that complete data can be restored whensnapshot restore backup.dbis executed?All reactions