Kbase P60840: Not enough space on one disk for the result of "probkup"
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
SYMPTOM(s):
Not enough space on one disk for the database backup made with "probkup"
"-com" option (for compressing the Progress backup) is already used
There would be enough cumulated space on different disks
FIX:
Backup within several files instead of within just one, using the option "-vs" of probkup as per:
probkup /path/dbname /path/dbpart1 -vs <###> < /path/input_file
with:
. dbname: your database name
. dbpart1: the first file (backup volume) to be created
. <###>: the volume size (the unit is the database block size)
. input_file: the file with the list of other backup volumes
You need to calculate the right value for the "-vs" parameter so that each file will fit in all disks to use. For knowing the database block size, specific to each database, you can check the following message within the log file "dbname.lg":
BROKER 0: Database Blocksize (-blocksize): 1024. (6573)
See below a sample for the contain of "input_file":
/path2/dbpart2
/path3/dbpart3
The database restore will need to "get" the list of files and, for the sample above, the solution can be:
prorest /path/dbname /path/dbpart1 < /path/dbotherparts
with "dbotherparts" containing:
y
/path2/dbpart2
/path3/dbpart3
in the case of restoring the database where dbname.db already exists and of having to answer the overwrite prompt from "prorest".
The verification of the backup, prorest with option "-vf" or "-vp" can be done with:
prorest /path/dbname /path/dbpart1 -vp < /path/input_file