Bacula-users

Re: [Bacula-users] incremental backups too large

2011-01-14 17:29:40
Subject: Re: [Bacula-users] incremental backups too large
From: Bart Swedrowski <bart AT timedout DOT org>
To: Martin Simmons <martin AT lispworks DOT com>, bacula-users AT lists.sourceforge DOT net
Date: Fri, 14 Jan 2011 22:26:26 +0000


On 14 January 2011 20:18, Martin Simmons <martin AT lispworks DOT com> wrote:
It sounds like you have some large files which compress a lot.

Nah, I don't think that is the case.  I know what are those files and those are mainly small, tiny files like emails, small log files.

Have a look at below's output.

14-Jan 02:38 tic.XXXXXX-fd JobId 1138:      Disallowed filesystem. Will not descend from / into /sys
14-Jan 02:38 donkey.XXXXXX-sd JobId 1138: Job write elapsed time = 00:31:03, Transfer rate = 137.8 K Bytes/second
14-Jan 02:38 bacula-dir01.XXXXXX-dir JobId 1138: Bacula bacula-dir01.XXXXXX-dir 5.0.3 (04Aug10): 14-Jan-2011 02:38:12
  Build OS:               i686-redhat-linux-gnu redhat 
  JobId:                  1138
  Job:                    tic_FS.2011-01-14_02.05.00_06
  Backup Level:           Incremental, since=2011-01-13 02:05:03
  Client:                 "tic.XXXXXX-fd" 5.0.3 (04Aug10) x86_64-redhat-linux-gnu,redhat,
  FileSet:                "tic FileSet" 2010-09-24 12:13:23
  Pool:                   "pws Pool" (From Job resource)
  Catalog:                "PWS" (From Client resource)
  Storage:                "pws.Storage" (From Pool resource)
  Scheduled time:         14-Jan-2011 02:05:00
  Start time:             14-Jan-2011 02:05:03
  End time:               14-Jan-2011 02:38:12
  Elapsed time:           33 mins 9 secs
  Priority:               10
  FD Files Written:       4,141
  SD Files Written:       4,141
  FD Bytes Written:       40,119,463,364 (40.11 GB)
  SD Bytes Written:       256,785,265 (256.7 MB)
  Rate:                   20170.7 KB/s
  Software Compression:   0.7 %
  VSS:                    no
  Encryption:             yes
  Accurate:               yes
  Volume name(s):         pws-0018
  Volume Session Id:      220
  Volume Session Time:    1291420212
  Last Volume Bytes:      25,503,971,841 (25.50 GB)
  Non-fatal FD errors:    0
  SD Errors:              0
  FD termination status:  OK
  SD termination status:  OK
  Termination:            Backup OK

14-Jan 02:38 bacula-dir01.timedout.org-dir JobId 1138: Begin pruning Jobs older than 14 days .
14-Jan 02:38 bacula-dir01.timedout.org-dir JobId 1138: Pruned 2 Jobs for client tic.timedout.org-fd from catalog.
14-Jan 02:38 bacula-dir01.timedout.org-dir JobId 1138: Begin pruning Jobs.
14-Jan 02:38 bacula-dir01.timedout.org-dir JobId 1138: No Files found to prune.
14-Jan 02:38 bacula-dir01.timedout.org-dir JobId 1138: End auto prune.

Now the bit that is particularly interesting to me is:

  FD Bytes Written:       40,119,463,364 (40.11 GB)
  SD Bytes Written:       256,785,265 (256.7 MB) 

Nothing has been written to the FD.  FD was being read during the backup time only.  And the amount shown as "SD Bytes Written" is what I would expect this incremental backup to take.  Now the question is why Bacula is now showing this in the "list jobs" or "status client" commands?

Thanks for follow-up.
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users