Enter the following command:

probkup online devel /dev/rrm/0m -vs 35 -bf 20 -verbose -thread 1

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; -verbose displays information at 10-second intervals during the backup, and -thread 1 enables multi-threading. 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:

Number of threads not specified. The default number of threads used is 4. (20669)
Write buffer factor (-wbf): 1024 (20786) 
Backup has spawned 4 worker threads. (20857)

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.

The write buffer factor specifies the number of 64KB write buffers when writing data to the backup file.

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.