Administer InfluxDB Enterprise

Back up and restore InfluxDB Enterprise clusters

When deploying InfluxDB Enterprise in a production environment, we recommend that you prepare for unexpected data loss with a strategy for backing up and restoring your InfluxDB Enterprise clusters. Plan your back up and restore strategy For each of the following scenarios, plan a back up and restore strategy that suits your needs: Disaster recovery due to unexpected events Migrating data to new environments or servers Restoring clusters to a consistent state Debugging To choose a strategy that best suits your use case, we recommend considering your volume of data, application requirements, acceptable recovery time, and budget.

Configure InfluxDB Enterprise clusters

Covers the InfluxDB Enterprise configuration settings, including global options, meta node options, and data node options

Configure InfluxDB Enterprise data nodes

Covers the InfluxDB Enterprise data node configuration settings and environmental variables

Configure InfluxDB Enterprise meta modes

Covers the InfluxDB Enterprise meta node configuration settings and environmental variables

Configure LDAP authentication in InfluxDB Enterprise

Configure LDAP authentication in InfluxDB Enterprise and test LDAP connectivity.

InfluxDB Anti-Entropy API

Use the InfluxDB Anti-Entropy API to monitor and repair shards on InfluxDB Enterprise data nodes.

Log and trace InfluxDB Enterprise operations

Covers logging locations, redirecting HTTP request logging, structured logging, and tracing.

Manage InfluxDB Enterprise clusters

Use the “influxd-ctl” and “influx” command line tools to manage InfluxDB Enterprise clusters and data.

Manage security in InfluxDB Enterprise

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.

Rename hosts in InfluxDB Enterprise

Host renaming The following instructions allow you to rename a host within your InfluxDB Enterprise instance. First, suspend write and query activity to the cluster. Rename meta nodes 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.

TCP and UDP ports used in InfluxDB Enterprise

Enabled ports 8086 The default port that runs the InfluxDB HTTP service. Configure this port in the data node configuration file. Resources API Reference 8088 The default port used for RPC calls used for inter-node communication and by the CLI for backup and restore operations (influxdb backup and influxd restore). Configure this port in the configuration file. Resources Backup and Restore Disabled ports 2003 The default port that runs the Graphite service.

Upgrade InfluxDB Enterprise clusters

To successfully upgrade InfluxDB Enterprise clusters to 1.7.10, complete the following steps: Back up your cluster. Upgrade meta nodes. Upgrade data nodes. Note: To downgrade to an earlier version, complete the following procedures, replacing the version numbers with the version that you want to downgrade to. Back up your cluster Before performing an upgrade, create a full backup of your InfluxDB Enterprise cluster. Also, if you create incremental backups, trigger a final incremental backup.

Use Anti-Entropy service in InfluxDB Enterprise

Prior to InfluxDB Enterprise 1.7.2, the Anti-Entropy (AE) service was enabled by default. When shards create digests with lots of time ranges (10s of thousands), some customers have experienced significant performance issues, including CPU usage spikes. If your shards include a small number of time ranges (most have 1 to 10, some have up to several hundreds) and you can benefit from the AE service, enable AE and monitor it closely to see if your performance is adversely impacted.