 |
Sparse files ? without sparse file setting in fileset Backing up the data that you backup e.g. forgot to exclude the backup area ? Not backing up any device files etc. e.g. the normal fileset work fine for others. If its backing up that data amount its there we do not make up anything just walk the filesystem open the files and backup the data. Try the estimate command on the client with the same fileset and check what included is what you expect to be part of the backup. Thousands of backups are made every day so this must be a local config problem. |
|
|
Here is the estimate. Seems to match the number of bytes copied. I cant understand how a disk of 65GB would hold 763.4 GB of data...thats puzzling Using Catalog "MyCatalog" Connecting to Client freeipa01-fd at freeipa01:9102 2000 OK estimate files=87,679 bytes=763,406,448,298 FD Bytes Written: 763,405,009,097 (763.4 GB) SD Bytes Written: 763,418,862,188 (763.4 GB) Here is the filesetFileSet { Name = "Linux All" Include { Options { Signature = MD5 # calculate md5 checksum per file One FS = No # change into other filessytems FS Type = ext2 # filesystems of given types will be backed up FS Type = ext3 # others will be ignored FS Type = ext4 FS Type = xfs FS Type = reiserfs FS Type = jfs FS Type = btrfs } File = / File = /boot File = /var File = /home File = /opt } Exclude block Exclude { File = /var/lib/bareos File = /var/lib/bareos/storage File = /proc File = /tmp File = /.journal File = /.fsck } |
|
|
Found the problem, sparse files... but setting sparse to yes did not fix it either, had to exclude /var/log/lastlog [root@freeipa01 log]# du -h /var/log/lastlog 60K /var/log/lastlog [root@freeipa01 log]# du -h --apparent-size lastlog 354G lastlog [root@freeipa01 log]# |
|
|
Is this still reproducible with newer version like 22x? |
|
|
no answer |
- Anonymous
