You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
etcd's v2 storage is easy to backup because the snapshot is write once and the WAL is append only. So, a user can use tools like rclone, rsync, etc to backup etcd and know that they got a good backup. Moving forward with the new storage system do we need to write or document new tools?
The text was updated successfully, but these errors were encountered:
@philips Even for v2, we do not encourage people to write their own tool:
We are not ready to give them any file level guarantees at runtime (for example, etcd will hold a file lock or etcd will help to mark a removable file.).
We want to wipe out the configuration for backup. Simply copy the file can be dangerous.
So people should use etcdctl backup. And we know a few people successfully using it. We do not have a plan to support "easy" backup yet.
@colhom and I have discussed about this for v3. And this is what we come up with: #2366 (comment)
etcd's v2 storage is easy to backup because the snapshot is write once and the WAL is append only. So, a user can use tools like rclone, rsync, etc to backup etcd and know that they got a good backup. Moving forward with the new storage system do we need to write or document new tools?
The text was updated successfully, but these errors were encountered: