General Steps for Backing Up Databases

At any time, a running database’s archive and journal provide the current state of that database. Therefore if you run multiple SMs for redundancy (as we recommend) you already have multiple copies (backups if you like) of your database.

Performing online (hot copy) or offline backups will be in addition to this. Consider how many more backups you need. In most cases if you need to take down an SM, or it fails for any reason, you can bring it back up and it will SYNC from the other SMs until it is up to date and available to service requests again.

NuoDB recommends the following when performing backups:

  1. Define site-specific backup policies and guidelines such as:

    • Naming conventions for directories that will contain database backups

    • Schedule of how often to run your backups

    • Any post-processing of database copy destination directories, for example, compressing them with an external tool or moving them to a remote location

      • Note that there is no space gained by compressing encrypted backups when TDE is enabled.

    • If using storage groups, multiple SMs must be backed up together such that the storage groups served by those SMs cover all storage groups in the database.

      • A coordinated hot copy backup will be required.

  2. According to your backup policies, use offline backup or online backup to regularly obtain a copy of the current state of each database.

  3. Store the copy in a secure location. Ensure that each stored copy includes both the archive and the journal. Backing up just the archive is pointless, it is useless on its own.