The database administrator of Company X's development department performs a full backup of the devel.db database every Friday on 9-track tapes. The DBA prepares the backup media according to the operating system documentation, then performs a full online backup of the devel.db.
The command, devel identifies the name of the database you are backing up; online specifies that the backup is an online backup; /dev/rrm/0m specifies the output destination is a tape drive; -vs 35 indicates that the volume size in database blocks is 35; -bf 20 specifies that the blocking factor is 20; and -verbose displays information at 10-second intervals during the backup. If you do not specify the volume size, PROBKUP fills the entire tape before prompting you for a new tape.
As the full offline backup of devel.db begins, the following report appears:
64 bi blocks will be dumped.
336 out of 336 blocks in devel will be dumped.
This will require 369664 bytes of backup media.
This backup will require a minimum of 400 blocks to restore.
1 volume will be required.
Backed up 400 blocks in 00:00:05.
Wrote a total of 18 backup blocks using 369664
bytes of media.
Backup complete.
The number of backup blocks is the number of -bf units written to the tape. Backup blocks contain data, primary recovery, and error-correction blocks.
This example backs up a very small database. Using the -red parameter on a larger database increases the amount of time and backup media required for the backup. Also, PROBKUP displays the number of blocks and the amount of backup required for an uncompressed database because you cannot specify the -scan parameter for an online backup.
3. If you enable after-imaging, back up the AI files to a separate tape or disk using a UNIX backup utility.
Note: If you enable after-imaging, OpenEdge automatically switches AI extents before beginning an online backup.
