Consultor Eletrônico

Status: Unverified

GOAL:

Quick method to determine the number of blocks of media you need when you perform a Progress backup.

GOAL:

How to know the amount of blocks of media needed for a Progress backup?

GOAL:

How To Estimate Blocks Of Media Needed For PROBKUP?

FIX:

Some options that can apply to the PROBKUP command can provide you with the necessary information:

- scan

This option performs an initial scan of the database and displays the number of blocks that will be backed up, and the amount of media the backup requires.

- verbose

This option provides a block by block listing while the backup is in the process of displaying the number of blocks currently backed up in ten second intervals.

You can use these options with the PROBKUP command. By redirecting output to a non-existent location on disk (/dev
ull) you are able to determine the amount of media required for a backup without actually performing one.

NOTE: Redirection to /dev
ull is only done for the purpose of media planning. It is not an actual backup.

An example using -scan to /dev
ull reports the following:

PROBKUP kbase /dev
ull -scan

230 active blocks out of 240 blocks in kbase will be dumped.
0 bi blocks will be dumped.
Backup requires 239 blocks (1 Mb) of media.
Restore would require 230 blocks (1 Mb) of media.
Backed up 230 blocks in 00:00:01
Wrote a total of 7 backup blocks using 1 megabytes of media. (5431)
Sometimes you might want to save as much media as possible. You can compress during the backup by using the -com option to PROBKUP.

An example using -scan and -com to /dev
ull reads:

PROBKUP kbase /dev
ull -scan -com

230 active blocks out of 240 blocks in kbase will be dumped.
0 bi blocks will be dumped.
Backup requires 171 blocks (1 Mb) of media.
Restore would require 230 blocks (1 Mb) of media.
Backed up 230 blocks in 00:00:00
Wrote a total of 5 backup blocks using 1 megabytes of media. (5431)