From: Gary D. <gar...@to...> - 2013-07-30 19:13:07
|
On 30/07/13 02:39 PM, John Drescher wrote: > On Tue, Jul 30, 2013 at 2:10 PM, Gary Dale<gar...@to...> wrote: >> On 30/07/13 12:41 PM, John Drescher wrote: >>> On Tue, Jul 30, 2013 at 12:27 PM, Gary Dale<gar...@to...> wrote: >>>> On 30/07/13 06:54 AM, Uwe Schuerkamp wrote: >>>>> On Mon, Jul 29, 2013 at 11:54:16PM -0400, Gary Dale wrote: >>>>>> I'm running Version: 5.2.6 (21 February 2012) x86_64-pc-linux-gnu debian 7.0 >>>>>> >>>>>> This schedule seems to almost be working. Unfortunately, I'm getting a >>>>>> full backup every Sunday before the differential backup on the 2nd-5th >>>>>> Sundays. The daily incremental backups are working properly. >>>>>> >>>>>> I've restarted the director several times so I'm pretty sure it's >>>>>> re-read the conf file. Any idea on what I'm doing wrong? >>>>>> >>>>>> Schedule { >>>>>> Name = "WeeklyCycle" >>>>>> Run = Full 1st sun at 23:05 >>>>>> Run = Differential 2nd-5th sun at 23:05 >>>>>> Run = Incremental mon-sat at 23:05 >>>>>> } >>>>>> >>>>> Hello Gary, >>>>> >>>>> I think we need more info on this one... how long are your retention >>>>> times? Is it possible your fulls expire within a week or get >>>>> overwritten so the differential gets somehow bumped to "full" status? >>>>> What's the bacula log file entry when the unexpected "full" starts? >>>>> >>>>> Uwe >>>> The Client part of the two computers being backed up each contains: >>>> >>>> File Retention = 30 days # 30 days >>>> Job Retention = 6 months # six months >>>> AutoPrune = yes # Prune expired Jobs/Files >>>> >>>> The Full& Differential backups get written to a Weekly backup (disk) >>>> pool, which is then copied to an external HD for offsite backup. Neither >>>> the Weekly or Daily pool is anywhere near full. Both have labelled empty >>>> volumes available. >>>> >>>> The report on the full backup of one machine is: >>>> >>>> 28-Jul 23:07 molar-dir JobId 1599: Start Backup JobId 1599, Job=BackupServer.2013-07-28_23.05.00_43 >>>> 28-Jul 23:07 molar-dir JobId 1599: Using Device "FileStorage" >>>> 28-Jul 23:07 molar-sd JobId 1599: Volume "weekly-backup-3" previously written, moving to end of data. >>>> 28-Jul 23:07 molar-sd JobId 1599: Ready to append to end of Volume "weekly-backup-3" size=4432241076 >>>> 28-Jul 23:07 server-fd JobId 1599: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C" >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "SqlServerWriter", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 server-fd JobId 1599: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:17 molar-sd JobId 1599: Job write elapsed time = 00:09:51, Transfer rate = 32.61 M Bytes/second >>>> 28-Jul 23:17 molar-dir JobId 1599: Bacula molar-dir 5.2.6 (21Feb12): >>>> Build OS: x86_64-pc-linux-gnu debian 7.0 >>>> JobId: 1599 >>>> Job: BackupServer.2013-07-28_23.05.00_43 >>>> Backup Level: Full >>>> Client: "server-fd" 5.2.6 (21Feb12) Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64 >>>> FileSet: "server-files" 2012-04-09 17:41:13 >>>> Pool: "WeeklyFile" (From Job FullPool override) >>>> Catalog: "MyCatalog" (From Client resource) >>>> Storage: "File" (From Job resource) >>>> Scheduled time: 28-Jul-2013 23:05:00 >>>> Start time: 28-Jul-2013 23:07:15 >>>> End time: 28-Jul-2013 23:17:09 >>>> Elapsed time: 9 mins 54 secs >>>> Priority: 10 >>>> FD Files Written: 34,225 >>>> SD Files Written: 34,225 >>>> FD Bytes Written: 19,267,786,645 (19.26 GB) >>>> SD Bytes Written: 19,273,081,531 (19.27 GB) >>>> Rate: 32437.4 KB/s >>>> Software Compression: None >>>> VSS: yes >>>> Encryption: no >>>> Accurate: no >>>> Volume name(s): weekly-backup-3 >>>> Volume Session Id: 46 >>>> Volume Session Time: 1373920803 >>>> Last Volume Bytes: 23,720,558,823 (23.72 GB) >>>> Non-fatal FD errors: 0 >>>> SD Errors: 0 >>>> FD termination status: OK >>>> SD termination status: OK >>>> Termination: Backup OK >>>> >>>> 28-Jul 23:17 molar-dir JobId 1599: Begin pruning Jobs older than 6 months . >>>> 28-Jul 23:17 molar-dir JobId 1599: No Jobs found to prune. >>>> 28-Jul 23:17 molar-dir JobId 1599: Begin pruning Files. >>>> 28-Jul 23:17 molar-dir JobId 1599: No Files found to prune. >>>> 28-Jul 23:17 molar-dir JobId 1599: End auto prune. >>>> >>>> >>>> This is followed two minutes later with: >>>> >>>> 28-Jul 23:17 molar-dir JobId 1600: Start Backup JobId 1600, Job=BackupServer.2013-07-28_23.05.00_44 >>>> 28-Jul 23:17 molar-dir JobId 1600: Using Device "FileStorage" >>>> 28-Jul 23:17 molar-sd JobId 1600: Volume "weekly-backup-3" previously written, moving to end of data. >>>> 28-Jul 23:17 molar-sd JobId 1600: Ready to append to end of Volume "weekly-backup-3" size=23720558823 >>>> 28-Jul 23:17 server-fd JobId 1600: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C" >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "SqlServerWriter", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 molar-sd JobId 1600: Job write elapsed time = 00:02:18, Transfer rate = 8.541 M Bytes/second >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 server-fd JobId 1600: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) >>>> 28-Jul 23:19 molar-dir JobId 1600: Bacula molar-dir 5.2.6 (21Feb12): >>>> Build OS: x86_64-pc-linux-gnu debian 7.0 >>>> JobId: 1600 >>>> Job: BackupServer.2013-07-28_23.05.00_44 >>>> Backup Level: Differential, since=2013-07-21 23:07:16 >>>> Client: "server-fd" 5.2.6 (21Feb12) Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64 >>>> FileSet: "server-files" 2012-04-09 17:41:13 >>>> Pool: "WeeklyFile" (From Job DiffPool override) >>>> Catalog: "MyCatalog" (From Client resource) >>>> Storage: "File" (From Job resource) >>>> Scheduled time: 28-Jul-2013 23:05:00 >>>> Start time: 28-Jul-2013 23:17:12 >>>> End time: 28-Jul-2013 23:19:31 >>>> Elapsed time: 2 mins 19 secs >>>> Priority: 10 >>>> FD Files Written: 448 >>>> SD Files Written: 448 >>>> FD Bytes Written: 1,178,710,585 (1.178 GB) >>>> SD Bytes Written: 1,178,779,573 (1.178 GB) >>>> Rate: 8479.9 KB/s >>>> Software Compression: None >>>> VSS: yes >>>> Encryption: no >>>> Accurate: no >>>> Volume name(s): weekly-backup-3 >>>> Volume Session Id: 47 >>>> Volume Session Time: 1373920803 >>>> Last Volume Bytes: 24,900,225,324 (24.90 GB) >>>> Non-fatal FD errors: 0 >>>> SD Errors: 0 >>>> FD termination status: OK >>>> SD termination status: OK >>>> Termination: Backup OK >>>> >>>> 28-Jul 23:19 molar-dir JobId 1600: Begin pruning Jobs older than 6 months . >>>> 28-Jul 23:19 molar-dir JobId 1600: No Jobs found to prune. >>>> 28-Jul 23:19 molar-dir JobId 1600: Begin pruning Files. >>>> 28-Jul 23:19 molar-dir JobId 1600: No Files found to prune. >>>> 28-Jul 23:19 molar-dir JobId 1600: End auto prune. >>>> >>> I would examine what the 448 files are that were included in the >>> second backup. Also try disabling any antivirus to see if that is >>> causing the problem. >>> >>> John >> Interesting observation John. I note that the Differential backup on my >> Linux machine (molar) included 3,492 files that apparently changed since >> 14,136 files were backed up in the Full backup. This is just the /home >> directory. >> >> The files that were backed up are ones that had changed since the >> previous Full backup. It's like the Differential backup is ignoring the >> Full backup that just completed, but not the one that happened a week >> before. >> >> I suspect that there is a reasonable explanation for this since one >> would not expect a differential backup to immediately follow a full >> backup. Possibly the updated catalogue isn't being read or the Last Full >> Backup date isn't being updated immediately. At any rate, the problem >> remains that a Full backup is being performed each week. >> >> I don't suspect anti-virus software since I'm getting the same problem >> on both the Linux and Windows backups. No anti-virus software was >> running on the Linux machine. > Do you have attribute spooling enabled? > > John Not so far as I can tell. |