7.2. Standalone databases

This section discusses configuration options for backups of standalone databases.

This section includes:

7.2.1. Configuration parameters

The table below lists the configuration parameters relevant to backups:

Table 7.1. Configuration parameters backups; standalone databases
Parameter name Default value Description

dbms.backup.enabled

true

Enable support for running online backups.

dbms.backup.address

127.0.0.1:6362-6372

Listening server for online backups.

7.2.2. Running backups from a separate server

Consider the image below:

backup separate server

In this configuration, the backup client is run on a separate server. This is the recommended configuration for a standalone database.

The server that runs the backup client must have Neo4j installed, but does not need to host a database.

It is strongly recommended to run backups from a different server than the production server.

7.2.3. Running backups from the local server

Consider the image below:

backup local server

In this configuration, the backup program is run on the same server that hosts the Neo4j production database.

When the backup program is started, it will start up a new Java process. If there is a running Neo4j database, this will run in parallel to the Neo4j process. On a production system, Neo4j is typically configured to take maximum advantage of the system’s available RAM. If you run backups on a production system, the overall performance can be negatively affected, and in extreme cases can cause failure with an out-of-memory error. It is therefore strongly recommended to run backups from a different server than the production server.

If it is not possible to use a separate backup server, you can control the impact on the production system by explicitly defining how much memory to allocate to the backup process. See Section 7.1.5, “Memory configuration”.