Backup Configuration for On-Premises

OverOps recommends that you set up a recurring backup of the recorded data to a remote location after finishing the installation process. By default, the data is stored in the /opt/takipi-server/storage/s3 directory or configured in the settings.yml file. All the files in the s3 data layer are immutable, therefore backup can be run regardless of the Storage Server activity. The backup procedure serves two different purposes:

  • secure the data on a secondary server
  • or provide redundancy in case a server fails.
    Instructions below assume neither, for more information contact your support team.

To set up recurring backup:

  • From the Server terminal, run:
    crontab -e + 0 * * * * rsync -av -e ssh <PATH_TO_OVEROPS_HOME_DIRECTORY>/storage/s3 <USER>@<BACKUP_SERVER_IP>


  • crontab -e + 0 * * * * - indicates that the command is run hourly.
  • rsync -av -e ssh /opt/takipi-server/storage @<BACKUP_SERVER_IP> - indicates the backup server to which the content is synced.


The server requires SSH access to the backup server. Refer to the relevant rsync man page for further enhancements and troubleshooting.

crontab -e
0 * * * * rsync -av -e ssh /opt/takipi-server/storage [email protected]


Cluster shutdown stop allows all storage to be backed up using rsync (cold backup).

  • Everything under storage S3 can be resynced. All are immutable files.
  • For the databases:
    • MySQL - backup with rsync does not require a shutdown, see AppDynamics page for a sample of live backup instructions
    • LevelDB - backup with rsync requires a shutdown.


Tomcat directory does not require backing up.