Hi, yes server and client are runnning on the same machine. The files which get backed up are on an ext3 filesystem and the disk where the snapshots get written to is a reiserfs filesystem. You're right, if I check the size for each snapshot it shows me around 3.6GB, if I check the size via du for the bank incl. all the daily snapshots it also shows me 3.6GB. What I find a bit strange, and that's why I initially noticed it is, that df shows the space as occupied, e.g. after each run, 3,6GB are gone.
Regards Stefan Bernd Haug schrieb: > Stefan Knoll wrote: > >> I'm having trouble with dirvish. It looks like it occupies for each >> run the whole amount of disk space as for the initial backup, but let >> me start from the beginning: I have a Ubuntu 7.10 64bit server >> installation. The dirvish cron job is running each night. The data >> which gets backed up is 3.6GB. The master.conf looks like this: >> > > Uh, me r dum: I just now understood that the server and client are the > same machine. > > I also forgot some things the first time around: FS type for your > bank(s)? FS type for the backed up tree? > > My very strong suspicion is that it does not *really* occupy all that > space, unless your FS does not support hard links natively (FAT, > HFS...), because the backup time is so much shorter. > > It's easy to get a wrong impression from what your tools tell you. > > E.g., compare the output between du -sh * and du'ing each of the trees > separately as a first step. With me, the latter shows each vault at full > size, whereas the first invocation notices "repeat" inodes and shows > only the first tree as full size. > > Yours, Bernd > > Stefan Knoll wrote: > >> I'm having trouble with dirvish. It looks like it occupies for each run >> the whole amount of disk space as for the initial backup, but let me >> start from the beginning: >> I have a Ubuntu 7.10 64bit server installation. The dirvish cron job is >> running each night. The data which gets backed up is 3.6GB. >> The master.conf looks like this: >> bank: >> /mnt/storage/disk2/Snapshots >> image-default: %Y%m%d_%H%M >> log: gzip >> index: gzip >> exclude: lost+found/ >> Runall: >> Daten >> Bilder >> expire-rule: >> #MIN Hour Day Month DOW Expire >> * * * * 1,3,4,5,6,7 +14 days >> * * * * 2 + 6 month >> expire-default: +30 days >> >> the default.conf (exemplary for Daten ) looks like this: >> >> client:localhost >> tree: /mnt/storage/disk1/Daten >> xdev: 0 >> index: gzip >> >> The strange thing is, the initial sync runs approx. 10 mins for each of >> the two jobs. Each subsequent job runs 10 secs. max, which is o.k. >> because there are not many files which get changed. However each backup >> occupies exactly the same amount of disk space as the initial one. I >> have now 4 backups plus the initial one and they are occupying approx. >> 18,5GB >> My understanding was, that diskspace will only get allocated if a file >> actually gets changed, so why does the occupied space grows and grows??? >> >> Thanks for your help >> Regards >> Stefan >> >> >> _______________________________________________ >> Dirvish mailing list >> [email protected] >> http://www.dirvish.org/mailman/listinfo/dirvish >> > _______________________________________________ > Dirvish mailing list > [email protected] > http://www.dirvish.org/mailman/listinfo/dirvish > _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
