Kbase P26694: prorest of probkup to multiple tapes fails with 1103 error
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/17/2003 |
|
Status: Unverified
FACT(s) (Environment):
Solaris
FACT(s) (Environment):
Progress 8.3A
SYMPTOM(s):
prorest of probkup to multiple tapes fails with 1103 error:
Next block in sequence should be <block-num> but got <block-num> instead (1103)
prorest -vp fails with 1103 error
probkup was done to multiple tapes
probkup appeared to complete normally
CAUSE:
The problem is very likely to have been caused by having to change tapes during the probkup - there were some issues with this in earlier v8 versions. It could be that the block reported in the 1103 message -
Next block in sequence should be 202930 but got 202929 instead (1103)
is caused by a bug (the block counter not being updated correctly in the backup when a tape change has to be done).
FIX:
There is no way to recover from an 1103. The only way would be to redo the backup, but this time specify the -vs option to probkup, i.e.
probkup dbname device-name -vs n
The value of n should be set lower than the size of the tapes that are being used.
The -vs parameter indicates the volume size - that is, the number of blocks that can be written to each removable volume. NT uses a variable block size up to 4K. For all other operating systems, each block is the size of one disk block (1K on UNIX). Before PROBKUP writes each volume, it displays a message that tells you to prepare the next volume. After writing each volume, a message tells you to remove the volume.
If you do not use the Volume Size parameter, PROBKUP assumes there is no limit and writes the backup until completion or until the volume is full. When the volume is full, PROBKUP prompts you for the next volume.