> [!CAUTION]
> **Caution:** This documentation covers Edge for Private Cloud 4.18.05, which is no longer supported. Google does not provide security patches, bug fixes, or technical support for this version. The current supported version is 4.54.00. See the [Edge for Private Cloud documentation](https://docs.apigee.com/private-cloud/latest/overview) for the current version, or [All versions](https://docs.apigee.com/private-cloud/versions) to compare releases.

*Edge for Private Cloud v4.18.05*

> [!NOTE]
> **Note:** When backing up a complete Edge installation, you must back up all components. See "What to Backup" at [Backup and restore](https://docs.apigee.com/private-cloud/v4.18.05/backup-and-restore) for more.

Use the following command to perform a backup:

```
/opt/apigee/apigee-service/bin/apigee-service component_name backup
```

Where <var translate="no">component_name</var> is the name of the component. Possible values include:

- `apigee-cassandra` (Cassandra)
- `apigee-openldap` (OpenLDAP)
- `apigee-postgresql` (PostgreSQL database)
- `apigee-qpidd` (Qpidd)
- `apigee-sso` (Edge SSO)
- `apigee-zookeeper` (ZooKeeper)
- `edge-management-server` (Management Server)
- `edge-management-ui` (new Edge UI)
- `edge-message-processor` (Message Processor)
- `edge-postgres-server` (Postgres Server)
- `edge-qpid-server` (Qpid Server)
- `edge-router` (Edge Router)
- `edge-ui` (Classic UI)

For example:

```
/opt/apigee/apigee-service/bin/apigee-service apigee-cassandra backup
```

> [!WARNING]
> **Warning:** The backup utility writes the generated backup file to `/opt/apigee/backup/component_name` where <var translate="no">component_name</var> is the name of the component. Because you can generate many backup files, and because these files can get large, you can mount a separate disk at `/opt/apigee/backup` just for backup files.

> [!NOTE]
> **Note:** For components not associated with a data store, such as the Router or Message Processor, the backup command still creates a backup file containing configuration and other information.

> [!NOTE]
> **Note:** For PostgreSQL only, you can optionally create a network storage snapshot as an alternative to using the Apigee backup command. This snapshot cab be useful because the Apigee backup command takes time to run and PostgreSQL data generated while the backup runs could be omitted from the resulting `.dump` file.

The backup command:

1. Stops the component (except for PostgreSQL and Cassandra which must be running to backup).
2. Creates a tar file of the following directories and files, where <var translate="no">component_name</var> is the name of the component:
   1. Directories
      - `/opt/apigee/data/component_name`
      - `/opt/apigee/etc/component_name.d`
   2. Files if they exist
      - `/opt/apigee/token/application/component_name.properties`
      - `/opt/apigee/customer/application/component_name.properties`
      - `/opt/apigee/customer/defaults.sh`
      - `/opt/apigee/customer/conf/license.txt`
3. Creates a .tar.gz file in the `/opt/apigee/backup/component_name` directory. The file name has the following form:

   ```
   backup-year.month.day,hour.min.seconds.tar.gz
   ```

   For example:

   ```
   backup-2018.05.29,11.13.42.tar.gz
   ```

   For PostgreSQL, the file name has the following form:

   ```
   year.month.day,hour.min.seconds.dump
   ```
4. Restarts the component (except for PostgreSQL, Cassandra, ZooKeeper, and OpenLDAP which are not restarted).

If you have multiple Edge components installed on the same node, you can back up them all with
a single command:

```
/opt/apigee/apigee-service/bin/apigee-all backup
```

This command creates a backup file for each component on the node.