34 lines
1.8 KiB
Markdown
34 lines
1.8 KiB
Markdown
---
|
|
title: Migrate to a Chronograf HA configuration
|
|
description: >
|
|
Migrate a Chronograf single instance configuration using BoltDB to a Chronograf high-availability (HA) cluster configuration using etcd.
|
|
menu:
|
|
chronograf_1_8:
|
|
weight: 10
|
|
parent: Administration
|
|
---
|
|
|
|
Use [`chronoctl`](/chronograf/v1.8/tools/chronoctl/) to migrate your Chronograf configuration store from BoltDB to a shared `etcd` data store used for Chronograf high-availability (HA) clusters.
|
|
|
|
> **Note:** Migrating Chronograf to a shared data source creates new source IDs for each resource. Update external links to Chronograf dashboards to reflect new source IDs.
|
|
|
|
1. Stop the Chronograf server by killing the `chronograf` process.
|
|
2. To prevent data loss, we **strongly recommend** that you back up your Chronograf data store before migrating to a Chronograf cluster.
|
|
3. [Install and start etcd](/chronograf/v1.8/administration/create-high-availability/#install-and-start-etcd).
|
|
4. Run the following command, specifying the local BoltDB file and the `etcd` endpoint beginning with `etcd://`. (We recommend adding the prefix `bolt://` to an absolute path. To specify a relative path to the BoltDB file, the prefix cannot be used.)
|
|
|
|
```sh
|
|
$ chronoctl migrate -f bolt:///path/to/chronograf-v1.db -t etcd://localhost:2379
|
|
```
|
|
|
|
> **Note:**
|
|
If you have authentication on `etcd`, use the standard URI format to define a username and password. For example, `etcd://user:pass@localhost:2379`
|
|
|
|
5. Update links to Chronograf (for example, from external sources) to reflect your new URLs:
|
|
- **from BoltDB:**
|
|
http://localhost:8888/sources/1/status
|
|
- **to etcd:**
|
|
http://localhost:8888/sources/373921399246786560/status
|
|
6. Set up a load balancer for Chronograf.
|
|
7. [Start Chronograf](/chronograf/v1.8/administration/create-high-availability/#start-chronograf).
|