Change:
Before starting the restore operation, a snapshot file must be present. It can either be a snapshot file from a previous backup operation, or from a remaining [data directory](https://etcd.io/docs/current/op-guide/configuration/#--data-dir). Here is an example: ```shell <del> ETCDCTL_API=3 etcdctl --endpoints 10.2.0.9:2379 snapshot restore snapshotdb </del> <ins> ETCDCTL_API=3 etcdctl --endpoints 10.2.0.9:2379 snapshot restore snapshot.db </ins> ``` <del> Another example for restoring using etcdctl options: </del> <ins> Another example for restoring using `etcdctl` options: </ins> ```shell <del> ETCDCTL_API=3 etcdctl snapshot restore --data-dir <data-dir-location> snapshotdb </del> <ins> ETCDCTL_API=3 etcdctl --data-dir <data-dir-location> snapshot restore snapshot.db </ins> ``` <del> Yet another example would be to first export the environment variable </del> <ins> where `<data-dir-location>` is a directory that will be created during the restore process. Yet another example would be to first export the `ETCDCTL_API` environment variable: </ins> ```shell export ETCDCTL_API=3 <del> etcdctl snapshot restore --data-dir <data-dir-location> snapshotdb </del> <ins> etcdctl --data-dir <data-dir-location> snapshot restore snapshot.db </ins> ``` For more information and examples on restoring a cluster from a snapshot file, see

Discussion:
The restoration command should be clear containing the new -to-be-created directory and the path containing the backup file. Like:
/language en /kind support
Hey are you talking about this ?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten
Hi The command - seems fine to me
As it is already mentioned that snapshotdb is a backup file.
/remove-kind support Seems reasonable to do /lifecycle frozen /priority backlog /triage accepted /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /remove-kind support Seems reasonable to do /priority backlog /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign