Introduction Shard entropy refers to inconsistency among shards in a shard group. This can be due to the “eventually consistent” nature of data stored in InfluxDB Enterprise clusters or due to missing or unreachable shards. The anti-entropy (AE) service ensures that each data node has all the shards it owns according to the metastore and that all shards in a shard group are consistent. Missing shards are automatically repaired without operator intervention while out-of-sync shards can be manually queued for repair.
Overview The primary use cases for backup and restore are:
Disaster recovery Debugging Restoring clusters to a consistent state InfluxDB Enterprise supports backing up and restoring data in a cluster, a single database and retention policy, and single shard.
Note: You can use the new backup and restore utilities in InfluxDB OSS 1.5 to:
Restore InfluxDB Enterprise 1.5 backup files to InfluxDB OSS 1.5. Back up InfluxDB OSS 1.5 data that can be restored in InfluxDB Enterprise 1.
Configure LDAP authentication in InfluxDB Enterprise and test LDAP connectivity.
Covers the InfluxDB Enterprise configuration settings, including global options, meta node options, and data node options
Host renaming The following instructions allow you to rename a host within your InfluxDB Enterprise instance.
First, spend write and query activity to the cluster.
Meta node: Find the meta node leader with curl localhost:8091/status. The leader field in the JSON output reports the leader meta node. We will start with the two meta nodes that are not leaders. On a non-leader meta node, run influxd-ctl remove-meta. Once removed, confirm by running influxd-ctl show on the meta leader.
Use the “influxd-ctl” and “influx” command line tools to interact with your InfluxDB Enterprise cluster and data.
Covers the InfluxDB Enterprise data node configuration settings and environmental variables
Covers the InfluxDB Enterprise meta node configuration settings and environmental variables
Covers logging locations, redirecting HTTP request logging, structured logging, and tracing.
Some customers may choose to install InfluxDB Enterprise with public internet access, however doing so can inadvertently expose your data and invite unwelcome attacks on your database. Check out the sections below for how protect the data in your InfluxDB Enterprise instance.
Enabling authentication Password protect your InfluxDB Enterprise instance to keep any unauthorized individuals from accessing your data.
Resources: Set up Authentication
Managing users and permissions Restrict access by creating individual users and assigning them relevant read and/or write permissions.
Upgrading InfluxDB Enterprise 1.3.x-1.5.x clusters to 1.6.6 (rolling upgrade) Step 0: Back up your cluster before upgrading to version 1.6.6. Create a full backup of your InfluxDB Enterprise cluster before performing an upgrade. If you have incremental backups created as part of your standard operating procedures, make sure to trigger a final incremental backup before proceeding with the upgrade.
Note: For information on performing a final incremental backup or a full backup, see the InfluxDB Enterprise Backup and restore documentation.