Kbase 17008: Inaccurate data reporting with probkup if over 2GB
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Inaccurate data reporting with probkup if over 2GB
The probkup function has a problem with reporting accurate data
backup if the amount to be backed up is over 2GB.
The reported restore requirements (in blocks) is correct, along
with the amount of data reported as backed up (in blocks).
The backup requirements (in bytes) and the total backup blocks,
along with total byte written to backup is inaccurate.
These are shown as negative numbers that do not translate out
to anything.
The following shows correct reporting using a 200MB database..
------------------------------
217269 active blocks out of 239997 blocks in /appl/mfgpro/viking2
will be dumped.
0 bi blocks will be dumped.
Backup requires 218213 blocks (223450112 bytes) of media.
Restore would require 217269 blocks (222483456 bytes) of media.
Backed up 217269 blocks in 00:05:16
Wrote a total of 614 backup blocks using 223450112 bytes of media.
Backup complete. (3740)
------------------------------
Following is an actual example of inaccurate reporting..
------------------------------
4164267 active blocks out of 4164382 blocks in
/appl/mfgpro/viking2 will be dumped.
0 bi blocks will be dumped.
Backup requires 4182001 blocks (-12598272 bytes) of media.
Restore would require 4164267 blocks (-30758888 bytes) of media.
Backed up 4164267 blocks in 01:41:45
Wrote a total of 123000 backup blocks using -12598272 bytes
of media.
Backup complete. (3740)
------------------------------
Note: This is a probkup reporting problem only. The correct amount
of data will be backed up correctly beyond 2GB.
This problem occurs with releases of 7.3C and 7.3D.
This bug is fixed in releases of 7.3E and above.
Progress Software Technical Support Note # 17008