On Fri, 30 May 2003 at 9:30am, Rebecca Pakish Crum wrote > Total Full Daily > -------- -------- -------- > Estimate Time (hrs:min) 0:02 > Run Time (hrs:min) 3:57 > Dump Time (hrs:min) 0:58 0:58 0:00 > Output Size (meg) 5798.6 5787.0 11.7 > Original Size (meg) 5798.6 5787.0 11.7 > Avg Compressed Size (%) -- -- -- (level:#disks > ..) > Filesystems Dumped 10 9 1 (1:1) > Avg Dump Rate (k/s) 1717.8 1716.1 3433.8 > > Tape Time (hrs:min) 1:32 1:32 0:00 > Tape Size (meg) 5798.9 5787.2 11.7 > Tape Used (%) 50.1 50.0 0.1 (level:#disks > ..) > Filesystems Taped 10 9 1 (1:1) > Avg Tp Write Rate (k/s) 1072.5 1072.4 1102.8 >
> NOTES: > planner: Dump too big for tape: full dump of isymmdb:/var delayed. > taper: tape isymmdaily01 kb 5938112 fm 10 [OK] > As I look back through my reports (2 days earlier my backup was 5950.2 > and it says my tape size was 5950.5) I see that my tape size is always > reading .3 over my estimated dump size. > > First, is this normal that my tape size never displays what it actually > is. Nope, that's normal. Output Size is the size of all the dump images. Remember that amanda puts a 32KB header on each of those before they go to tape. 10 filesystems * 32KB is 320KB, or about .3 MB. QED. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University