Skip to main content
You are viewing the documentation for Interana version 2. For documentation on the most recent version of Interana, go to


Scuba Docs

How backups work


As a Managed Edition customer, your Interana cluster is backed up on a daily basis. During the backup process your company's data is archived along with Interana query and metadata. In the case of a data loss event, your data can be restored to the last backup. This article explains the Interana backup process for Interana Managed Edition customers, and includes the following topics:

Backup schedule and downtime

Interana performs daily backups for Managed Edition customers at 4:55 am, Pacific Standard Time (PST). During this time (of the final backup), the Interana cluster is unavailable for five minutes to one hour, depending on the size of your cluster.

If the standard Interana backup schedule is not convenient for your time zone, contact your Interana Customer Success Manager (or to establish a backup time that meets your needs.

Backups behind the scenes

Backing up your Interana cluster is a daily process. This section explains the difference between a final backup and incremental backup, how they work together, and the processes that happen behind the scenes during a final backup.

Final and incremental backups

final backup is performed daily at the same scheduled time. A final backup requires system downtime from between five minutes and one hour, depending on the size of the cluster.

An incremental backup is taken during the previous day to shorten system downtime of the final backup, and is incorporated into the final backup. An incremental backup does not interrupt the system and no services are stopped.

Final backup process

A final backup requires between five minutes and one hour of system downtime, depending on the size of the cluster.

A final backup of your Interana cluster incorporates the previous incremental backup, and captures all of your data and Interana metadata into backup folders. The final backup uses the following process:

  1. All Interana services are stopped on all nodes, both imports and queries.
  2. All file systems are frozen, on all cluster nodes.
  3. Snapshots are taken of all nodes in their frozen state.
  4. Data tier nodes and string tier nodes are synchronized from the main file system to the backup file system.
  5. File systems on all nodes are unfrozen.
  6. Services on all nodes are restarted.
  7. The cluster recovers after synchronizing all nodes and restarting services. This can take between five minutes to one hour depending on the size of the cluster.

For more information

Best practices for logging data—recommended practices for logging data for Interana.