Backing up a Netdata Agent
Introduction
When preparing to backup a Netdata Agent it is worth considering that there are different kinds of data that you may wish to backup independently or all together:
Data type | Description | Location |
---|---|---|
Agent configuration | Files controlling configuration of the Netdata Agent | config directory |
Metrics | Database files | /var/cache/netdata |
Identity | Claim token, API key and some other files | /var/lib/netdata |
Scenarios
Backing up to restore data in case of a node failure
In this standard scenario you are backing up your Netdata Agent in case of a node failure or data corruption so that the metrics and the configuration can be recovered. The purpose is not to backup/restore the application itself.
Verify that the directory-paths in the table above contain the information you expect.
Note
The specific paths may vary depending upon installation method, Operating System and whether it is a Docker/Kubernetes deployment.It is recommended that you stop the Netdata Agent when backing up the Metrics/database files.
Backing up the Agent configuration and Identity folders is straight-forward as they should not be changing very frequently.Using a backup tool such as
tar
you will need to run the backup as root or as the netdata user in order to access all the files in the directories.sudo tar -cvpzf netdata_backup.tar.gz /etc/netdata/ /var/cache/netdata /var/lib/netdata
Stopping the Netdata agent is mostly required in order to back up the database files of the Netdata Agent.
If you wish to minimize the gap in metrics caused by stopping the Netdata Agent, then you could have a backup job or script that uses the following sequence:
- Backup the Agent configuration Identity directories
- Stop the Netdata service
- Backup up up the database files
- Restart the netdata agent.
Restoring Netdata
Ensure that the Netdata agent is installed and is stopped
If you plan to deploy the Agent and restore a backup on top of it, then you might find it helpful to use the
--dont-start-it
option upon installation.wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh && sh /tmp/netdata-kickstart.sh --dont-start-it
Note If you are going to restore the database files then you should first ensure that the Metrics directory is empty.
sudo rm -Rf /var/cache/netdata
Restore the backup from the archive
sudo tar -xvpzf /path/to/netdata_backup.tar.gz -C /
Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.