The `consul snapshot agent` command starts a process that takes snapshots of the state of the Consul servers in Consul Enterprise. It can capture server state once or it can run as daemon that captures snapshots at defined intervals.
The `consul snapshot agent` command starts a process that takes snapshots of the state of the Consul servers in Consul Enterprise. It can capture server state once or it can run as a daemon that captures snapshots at defined intervals.
---
# Consul Snapshot Agent
@ -17,8 +17,8 @@ version 0.7.1 and later. All other [snapshot subcommands](/consul/commands/snaps
are available in the community edition of Consul.
The `snapshot agent` subcommand starts a process that takes snapshots of the
state of the Consul servers and saves them locally, or pushes them to an
optional remote storage service.
state of the Consul servers and saves them locally, or pushes them to optional
remote storage services.
The agent can be run as a long-running daemon process or in a one-shot mode
from a batch job, based on the [`-interval`](#interval) argument. Snapshotting
@ -36,10 +36,10 @@ leader and starting saving snapshots.
As snapshots are saved, they will be reported in the log produced by the agent:
```log
2016/11/16 21:21:13 [INFO] Snapshot agent running
2016/11/16 21:21:13 [INFO] Waiting to obtain leadership...
- `-local-scratch-path` - Location to store all temporary snapshots in prior to
sending them off to the configured storage backend. If not configured the
system temporary directory will be used. When using the local storage backend
this is not configurable and `-local-path` will be used.
system temporary directory will be used.
#### Agent Options
@ -263,14 +270,16 @@ if desired.
- `login-meta` - Metadata to set on the token, formatted as key=value. This flag may be provided multiple times.
#### Local Storage Options
This option cannot be used when using `backup_destinations` in a config file.
- `-local-path` - Location to store snapshots locally. The default behavior
of the snapshot agent is to store snapshots locally in this directory. Defaults
to "." to use the current working directory. If an alternate storage option is
configured, then local storage will be disabled and this option will be ignored.
to "." to use the current working directory. If an alternate remote storage
option is configured, then local storage will be disabled and this option will
be ignored.
#### S3 Storage Options
These options cannot be used when using `backup_destinations` in a config file.
Note that despite the AWS references, any S3-compatible endpoint can be specified with `-aws-s3-endpoint`.
- `-aws-access-key-id`, `-aws-secret-access-key` and `-aws-session-token` - These arguments supply static
@ -369,6 +378,8 @@ The following example IAM policy document assumes that the `aws-s3-bucket` is `c
From Consul Enterprise version `1.5.0` onwards, you can store snapshots in Azure Blob storage.
These options cannot be used when using `backup_destinations` in a config file.
- `-azure-blob-account-name` and `-azure-blob-account-key` - These arguments supply
authentication information for connecting to Azure Blob storage.
@ -382,12 +393,15 @@ From Consul Enterprise version `1.5.0` onwards, you can store snapshots in Azure
From Consul Enterprise version `1.6.1` onwards, you can store snapshots in Google Cloud Storage. Authentication relies on automatic discovery through the sdk as described [here](https://cloud.google.com/docs/authentication/production):
- First, ADC checks to see if the environment variable GOOGLE_APPLICATION_CREDENTIALS is set. If the variable is set, ADC uses the service account file that the variable points to. The next section describes how to set the environment variable.
- If the environment variable isn't set, ADC uses the default service account that Compute Engine, Kubernetes Engine, App Engine, and Cloud Functions provide, for applications that run on those services.
- If ADC can't use either of the above credentials, an error occurs.
This option cannot be used when using `backup_destinations` in a config file.
@ -39,6 +39,8 @@ We are pleased to announce the following Consul updates.
- **Downgrade from Consul Enterprise to Consul Community Edition**: Consul now provides the ability for enterprise users to migrate their deployments to Community edition and disable enterprise features for business continuity. Refer to [Downgrade from Consul Enterprise to the community edition](/consul/docs/enterprise/ent-to-ce-downgrades) for more information.
- **Consul Snapshot Agent support for multiple destinations (Enterprise):** Consul Enterprise users can now specify [multiple local and remote destinations](/consul/commands/snapshot/agent) for Consul snapshot backups.
## Upgrading
For more detailed information, please refer to the [upgrade details page](/consul/docs/upgrading/upgrade-specific) and the changelogs.
Semir Patel
9 months ago
committed by