Backups

A database backup can be a full offline backup, an online quiesced backup, or an online full backup. For details and a discussion about choosing a backup strategy, the danger of backing up the online transaction journal, and backing up your JADE development environment, see the following subsections.

For details about:

• The JADE initialization file parameters that enable you to configure your backups, see "Persistent Database Initialization Section [PersistentDb]", in the JADE Initialization File Reference.

• Using an SDS environment to keep secondary copies of a database synchronized with a primary updating copy and to provide read-only access to secondary copies of the database (for example, for the design and deployment of high workloads), see "Administering a JADE Synchronized Database Service (SDS) Environment", in Chapter 1 of the JADE Synchronized Database Service (SDS) Administration Guide.

The JADE Database utility backup compress operation uses temporary files (for example, *.lo$ and *.da$) that can remain if the operation fails. You can safely delete these *.lo$ and *.da$ files. These temporary files are renamed if the operation succeeds (for example, to *.lo_ and *.da_). The decompress operation also uses the dollar symbol ($) file name variant before renaming the intermediate file to the actual target name when the operation succeeds. Overwrite and non‑overwrite behavior applies to these temporary intermediate files.