# noust restore-server

Bring a whole server back from a bundle of Noust's own state.

```bash
noust restore-server [OPTIONS]
```

| Option | What it does | Default |
|---|---|---|
| `--from` | The bundle: a path, or its name on this server. |  |
| `--from-destination` | Fetch the bundle from this backup destination first (with --name). |  |
| `--name` | With --from-destination: the bundle's name there. |  |
| `--host` | With --from-destination: the old server's folder there. |  |
| `--app` | Restore only this application. Repeatable. |  |
| `--skip` | Leave this application out. Repeatable. |  |
| `--skip-state` | Noust's state is already back (a run that stopped): only bring the applications up. |  |
| `--force` | Restore over a server that already holds state. |  |
| `--install` | Install what this machine lacks: the web server, Docker (when an application or an instance needs it) and the database engines. Without it nothing is installed. |  |
| `--no-databases` | Do not bring back the databases no application owns. |  |
| `--accept-schema-changes` | Restore an application's files even past a schema change nothing restores the database for. |  |
| `--plan` | Say what the bundle would bring back, and stop. Changes nothing. |  |
| `--yes`, `-y` | Do not ask for confirmation. |  |
| `--passphrase-file` | Read the bundle's passphrase from this file (mode 600). |  |
| `--json` | Print the report as JSON. |  |
| `--reason` | Why this change is made (a change reference, a ticket). Recorded with the command in the audit log; required only where a compliance framework asks for it (ENS) or security.change_reasons is on. |  |