vdump size reporting

[Jason Sutton]

Im not sure if we have an issue here or not.

We are using a Tru64 machine with a robot to perform backups, some of the areas being backed up are mounted via NFS. When performing the backups i have noticed strange things in the reporting from vdump

Below is the output from the vdump and a df from the area being backed up.

Does anyone have any ideas why these numebrs dont match ???

[Jason Sutton]

Appologies, here is the output.

Filesystem 1024-blocks Used Available Capacity Mounted on
laalaalocal:/nfs/laalaa/sws 3922525 3311739 218533 94% /nfs/laalaa/sws


#/sbin/vdump -0 -C -v -D -f /dev/ntape/tape2c /nfs/laalaa/sws
path : /nfs/laalaa/sws
dev/fset : laalaalocal:/nfs/laalaa/sws
type : nfs
vdump: Date of last level 0 dump: the start of the epoch
vdump: Dumping directories
vdump: Dumping 1567027550 bytes, 63419 directories, 1072095 files
vdump: Dumping regular files
......

vdump: Status at Fri Mar 5 01:04:46 2004
vdump: Dumped 2867494715 of 1567027550 bytes; 183.0% completed
vdump: Dumped 63419 of 63419 directories; 100.0% completed
vdump: Dumped 1072095 of 1072095 files; 100.0% completed
vdump: Dump completed at Fri Mar 5 01:04:46 2004
vdump: Finished at 0305_0104, returned: 0

[Michael Schulte zur Sur]

Hi,

since the drive is not blocked while backup, it is possible, that usage and number of files since the begin of the vdump change.
Dumping 1567027550 bytes
Dumped 2867494715 of 1567027550 bytes; 183.0% completed

this means, that one file has increased a lot during the backup.

greetings,

Michael

[Ralf Puchner]

it seems the dump size changed during backup. The estimated file sizes increased during backup indicating someone is still writing to a file.

Backup open file is not a good idea, left the file in an unknown state.

[Mobeen_1]

Jason,
I simply think that you are backing up an active file system. Looks like your filesystem has some files which are open and this probably is the reason why your nos don't match.

regards
Mobeen

[Jason Sutton]

Thanks for the quick responses, admittedly the df was performed this morning but the backup last night at about 12. This could explain the difference between these figures, but it doesnt explanation for why 183% gets backed up ???

It's quite unlikely that anyone was doing anything at that time, and even so the disk utilisation growing by such a large amount ????

Anyone have any more ideas ??

[Michael Schulte zur Sur]

Jason,

vdump does a statistic of what it has to backup before it starts the backup. When after that files get bigger then you have backuped more than 100%. You can count on it, that during the backup the file set got bigger. Maybe not by this machine, but by another machine, which also has this nfs drive mounted.

Michael

[Jason Sutton]

I guess that could be the explanation, the fileset itself is on a HP-UX machine and mounted to a number of other machines.

Thanks all for the responses.

Jason...

[Michael Schulte zur Sur]

Hi,

you are wellcome. That's the reason for this place.

Michael

http://forums1.itrc.hp.com/service/forums/helptips.do?#28

[Michael Schulte zur Sur]

Hi Jason,

do you already know the points system?
http://forums1.itrc.hp.com/service/forums/helptips.do?#28

thanks,

Michael