DBMaker allows the use of different options for backing
up a database. In addition to periodic incremental or full backups made
by the backup daemons, executing a backup at any time the database is
on or off-line is supported.
On-line full backups increase the load on a system's processor
and storage, and should only be done when client resource demands are
low.

Figure:
The Backup window
You can use the following backup methods.
The boldface text
below can be linked to the corresponding headers of the following topics.
- On-Line
Full Backup by Backup Server: JServer Manager automatically backs
up the database to the location specified in the dmconfig.ini file. All
data in the database is copied to the backup location. The database must
be started and the Backup Server activated. Clients may be connected to
the database while on-line backup is being performed. File objects are
also backed up when this method is used.
- On-Line
Full Backup Interactively: The destination of backup files may
be specified. File objects are not backed up.
- On-line
Full Backup To Tape: All data in the database is copied to a single
tape. File objects are not backed up.
- Off-Line
Full Backup: All data in the database is copied to the backup location.
The database must not have been started before off-line full backup is
performed. File objects are not backed up.
- Off-line
Full Backup To Tape: All data in the database is copied to a single
tape. File objects are not backed up.
- Incremental
Backup By Backup Server: All journal blocks are copied to the incremental
backup location that is specified in the dmconfig.ini file. Incremental
backups can be performed while the database is on-line and clients are
connected to the database.
- Incremental
Backup Interactively: All journal blocks are copied to an incremental
backup location that may be specified at the time of the incremental backup.
Incremental backups can be performed while the database is on-line and
clients are connected to the database.
- Incremental
Backup to Current Interactively: The data in the database is backed
up from the point of the most recent backup to the end of the current
journal file. The advantage of performing an incremental backup to current
is that you can better protect the database against crashes.
Related topic:
Setting
Backup Options