General Steps for Backing Up Databases
NuoDB recommends the following steps to create database copies and store them as backups:
- Define site-specific backup policies and guidelines such as:
- Naming conventions for directories that will contain database copies
- Schedule of how often to make copies of databases
- Any post-processing of database copy destination directories, for example, compressing them with an external tool or moving them to a remote location
- According to your backup policies, use offline backup or online backup to regularly obtain a copy of the current state of each database. A running database’s archive and journal provide the current state of that database.
- Store the copy in a secure location. Ensure that each stored copy includes both the archive and the journal.
- Add a snapshot storage manager (SSM) to your database. This lets you take advantage of online snapshot backup. An SSM saves a snapshot of the database for every committed transaction. When you want to restore data to a particular committed transaction you copy the snapshot of interest from the SSM.
To use Incremental Backups, use the following steps:
- Start a SM (or SMs) with the options parameter using
journal-hot-copy set to 'enable'.
- Run Full Hot Copy of the database and specify the destination archive directory(ies), (optional) journal directory(ies), and participating SMs.
- Run Journal Hot Copies of the database at regular intervals, specifying the destination archive directory(ies), (optional) journal directory(ies), participating SMs,
- Run Incremental Hot Copies to decrease the time to restore (optional).
Note: With storage groups, participating SMs should be selected such that the storage groups served by those SMs cover all storage groups in the database.