<a id="command-juju-create-backup"></a>

# `juju create-backup`

> See also: [download-backup](https://documentation.ubuntu.com/juju/4.0/reference/juju-cli/list-of-juju-cli-commands/download-backup.md#command-juju-download-backup)

## Summary

Create a backup.

## Usage

```text
juju create-backup [options] [<notes>]
```

### Options

| Flag                       | Default                          | Usage                                                                      |
|----------------------------|----------------------------------|----------------------------------------------------------------------------|
| `-B`, `--no-browser-login` | false                            | Do not use web browser for authentication                                  |
| `--filename`               | juju-backup-<date>-<time>.tar.gz | Download to this file                                                      |
| `-m`, `--model`            |                                  | Model to operate in. Accepts [<controller name>:]<model name>|<model UUID> |
| `--no-download`            | false                            | Do not download the archive. DEPRECATED.                                   |

## Examples

```none
juju create-backup
juju create-backup --no-download
```

## Details

This command requests that Juju creates a backup of its state.
You may provide a note to associate with the backup.

By default, the backup archive and associated metadata are downloaded.

Use `--no-download` to avoid getting a local copy of the backup downloaded
at the end of the backup process. In this case it is recommended that the
model config attribute `backup-dir` be set to point to a path where the
backup archives should be stored long term. This could be a remotely mounted
filesystem; the same path must exist on each controller if using HA.

Use `--verbose` to see extra information about backup.

To access remote backups stored on the controller, see `juju download-backup`.
