In this guide, learn more about the various backup options and understand which parts of anynode are included in the backup process.

General Concept

With the backup function in anynode, you can save the entire anynode configuration, including all settings, recordings, logs, and certificates.

This provides the option of quickly restoring a complete anynode system.

This function proves beneficial in the following scenarios

  • Operating system failure

  • Complete replacement of a faulty hard drive

  • Migration to a more robust system / Migration to/from a virtual machine

  • Accidental deletion of anynode

  • Accidental configuration changes

The backup supplements the previous configuration export.

Utilizing the previous export function through Configuration and Export is recommended for efficiently creating backups of the node configuration. This allows for rapid testing without the risk of accidentally deleting the call history. In this case, only the SIP-based settings will be backed up and restored.

anynode does not support differential or incremental backups. At a minimum, we recommend a configuration backup after significant changes to the configuration.

The full backup integrates log files and recordings into your strategy. If you have an external database with an existing backup strategy, consider writing CDR data and logging files into this database.

What data can we restore?

The scope of the backup depends on the backup option you choose:

The full configuration backup

This option includes comprehensive settings and data related to the anynode frontend, anynode configuration, and anynode monitor configuration

  • anynode frontend configuration: user management, LDAP authorities, Azure AD authority, webserver connectors, backends, certificate issuances, certificates, ACME services, account and password settings, Microsoft Teams SBA, proxy server settings

  • anynode configuration: audio files (tones and announcements), static HTTP server resources, every configuration object, every auxiliary object

  • anynode monitor configuration (without call history and event log): SMTP clients, event transport, call history settings, event log settings, licenses warning settings, certificates warning settings, active sessions settings, disc space warning settings

The full backup

This option encompasses everything included in the full configuration backup, plus additional data. In addition to all the components listed under the full configuration backup, it also includes call history, event log data, and recorded sessions (subject to the requirement of having an anynode user with a media recorder rule).

  • anynode frontend configuration: user management, LDAP authorities, Azure AD authority, webserver connectors, backends, certificate issuances, certificates, ACME services, account and password settings, Microsoft Teams SBA, proxy server settings

  • anynode configuration: audio files (tones and announcements), static HTTP server resources, every configuration object, every auxiliary object

  • anynode monitor configuration: call history, event log, SMTP clients, event transport, call history settings, event log settings, licenses warning settings, certificates warning settings, active sessions settings, disc space warning settings

  • Recorded sessions: (an anynode user with a media recorder rule is required)

What data can we not restore?

Licenses: Due to licensing restrictions, licenses are not restored during backup and restore operations. Licenses must always be manually reinstalled. If needed, please refer to our video tutorial on licensing.

External database files: Only the database access is restored when utilizing external databases, such as Microsoft Entra ID. The directory in anynode will be repopulated with data from the database. For external call history and event databases, backup and restore operations are not conducted; these processes are exclusive to the internal (SQLite) database. Only the access to the external database is backed up and restored.

File structure

In essence, with every installation of anynode on Windows, there are two paths to consider:

C:\Program Files\TE-SYSTEMS and C:\ProgramData\TE-SYSTEMS (hidden folder) with a folder structure.

The Program Files folder contains the application files of anynode, while the Program Data folder stores the data used for working with anynode.

The individual folders for a full backup are as follows:

  • anynode (anynode configuration file)

  • anynode_frontend (anynode frontend file)

  • anynodemon (call history and events, monitor configuration file)

  • recordings (all media recordings)

  • info.txt (information about version numbers and list of recordings)

In Linux, the following program paths are utilized. For non-variable data:

/opt/tesystems/<name of the anynode service>

(anynode/anynodead/anynodefe/anynodemon)

For variable data (for instance configuration data, IPC data, trace data...):

/var/opt/tesystems/<name of the anynode service >

(anynode/anynodead/anynodefe/anynodemon)

The individual parameters for a full backup under Linux are as follows:

ANYNODE_CONFIG

MEDIA_FILES

HTTP_SERVER_FILES

FRONTEND_CONFIG

MONITOR_CONFIG

CALL_HISTORY

EVENT_LOG

MEDIA_FILES refer to the audio files configured in the node under "tones and announcements". To include recordings, you would need to add RECORDINGS to the list. Remember that you need a user with administrator and media recorder roles to access the recordings.