User Tools

Site Tools


NEMS Migrator


Local Backups


Your NEMS Linux server automatically generates a backup of your entire configuration ready for you to download at any time.

Your NEMS Migrator backup (filename: backup.nems) contains system information, logs, Nagios configuration, your database, and more. Despite this, it is rather small by design, with new NEMS Linux deployments rolling a backup of about 4MB with larger deployments hitting anywhere around 10MB in size.

A NEMS Migrator backup is proprietary to NEMS. It is not intended for user consumption, but rather can be used to restore NEMS Linux to a previous configuration, or quickly rebuild after an SD card failure (for example).

To use NEMS Migrator to upgrade from an earlier version of NEMS Linux (or even NagiosPi), please read Upgrade NEMS Linux to Newer Version.

To automated your NEMS Migrator backup, please see Backup Your NEMS Configuration Automatically for helpful resources and tips.


Please see nems-restore.

Off-Site Backup


NEMS Migrator Off-Site Backup (OSB) encrypts your NEMS Migrator backup on your local NEMS server and then transmits it to our cloud server over a secure connection where it is retained securely for 30 days.

Your NEMS Migrator Off-Site Backup is encrypted using a password you create locally in NEMS SST. Because of this, only you can restore from this file. Your private password is never sent to our server. Your account is authenticated based on your NEMS HWID and an “OSB Key” that is provided to you when you register.

Sign up on Patreon (observe the reward options) and then add your OSB License Key to NEMS-SST to activate the service.

Once activated, NEMS will automatically backup your configuration off-site every day at 4am.


The backup results are stored in /var/log/nems/nems-osb.log

Log Format

The log file is a single line of data sent by the server. Each variable is separated by two colons (::) and begin with variable 0.

  • 0 - Plain text date/time of your NEMS server's when the backup began
  • 1 - Response code after file sent
  • 2 - Plain-text interpretation of 1 (ie., Success or Failed)
  • 3 - Plain-text interpretation of 1 (ie., Reason for 2)

If (and only if) the backup was successful with a response code of 1, the following data will also be logged:

  • 4 - The remote server's unix timestamp at time of off-site backup authentication
  • 5 - The size of this backup
  • 6 - Your total usage on the remote storage server, including this backup
  • 7 - How many daily backups are currently retained for your account


Please see nems-restore.

features/nems-migrator.txt · Last modified: 2018/02/05 10:50 by Robbie Ferguson