Re: [Bacula-users] What's wrong with my schedule?
> On Wed, 31 Jul 2013 11:25:25 -0400, Gary Dale said: > > On 31/07/13 07:14 AM, John Drescher wrote: > Do you have attribute spooling enabled? > > John > >>> Not so far as I can tell. > >>> > >> Why would I want to have it enabled? > > Normally you enable that to speed up database inserts since this > > causes the DB inserts to happen at the end of the job (in large > > transactions) instead of after every single file. However in this case > > I was concerned that your differential was started before the > > attribute inserts were finished. Remember that bacula compares what is > > in the DB to what it finds in the filesystem to determine what has > > changed from the full. > > > > John > > > But that's not the problem. The problem is that Full backup is running. > If the Full backup was following the schedule, the issue of the > differential backing up the files wouldn't exist. The output of show job=BackupServer might reveal something. __Martin -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] What's wrong with my schedule?
On Wed, Jul 31, 2013 at 11:25 AM, Gary Dale wrote: > On 31/07/13 07:14 AM, John Drescher wrote: > Do you have attribute spooling enabled? > > John Not so far as I can tell. >>> Why would I want to have it enabled? >> Normally you enable that to speed up database inserts since this >> causes the DB inserts to happen at the end of the job (in large >> transactions) instead of after every single file. However in this case >> I was concerned that your differential was started before the >> attribute inserts were finished. Remember that bacula compares what is >> in the DB to what it finds in the filesystem to determine what has >> changed from the full. >> >> John >> > But that's not the problem. The problem is that Full backup is running. > If the Full backup was following the schedule, the issue of the > differential backing up the files wouldn't exist. > Sorry. I caught this thread mid stream and I assumed the issue was the Differential was backing up too many files instead of the Full running when it was not supposed to run. I read the initial post and I think if you restarted the director since you changed the schedule or reloaded the configuration files this has to be a bug. Although I run a similar schedule on several machines at work and I have not seen this behavior so I am not sure what triggers this.. John -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] What's wrong with my schedule?
On 31/07/13 07:14 AM, John Drescher wrote: Do you have attribute spooling enabled? John >>> Not so far as I can tell. >>> >> Why would I want to have it enabled? > Normally you enable that to speed up database inserts since this > causes the DB inserts to happen at the end of the job (in large > transactions) instead of after every single file. However in this case > I was concerned that your differential was started before the > attribute inserts were finished. Remember that bacula compares what is > in the DB to what it finds in the filesystem to determine what has > changed from the full. > > John > But that's not the problem. The problem is that Full backup is running. If the Full backup was following the schedule, the issue of the differential backing up the files wouldn't exist. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] What's wrong with my schedule?
>>> Do you have attribute spooling enabled? >>> >>> John >> Not so far as I can tell. >> > Why would I want to have it enabled? Normally you enable that to speed up database inserts since this causes the DB inserts to happen at the end of the job (in large transactions) instead of after every single file. However in this case I was concerned that your differential was started before the attribute inserts were finished. Remember that bacula compares what is in the DB to what it finds in the filesystem to determine what has changed from the full. John -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] What's wrong with my schedule?
On 30/07/13 03:12 PM, Gary Dale wrote:
> On 30/07/13 02:39 PM, John Drescher wrote:
>> On Tue, Jul 30, 2013 at 2:10 PM, Gary Dale wrote:
>>> On 30/07/13 12:41 PM, John Drescher wrote:
On Tue, Jul 30, 2013 at 12:27 PM, Gary Dalewrote:
> 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 m
Re: [Bacula-users] What's wrong with my schedule?
On 30/07/13 02:39 PM, John Drescher wrote:
> On Tue, Jul 30, 2013 at 2:10 PM, Gary Dale wrote:
>> On 30/07/13 12:41 PM, John Drescher wrote:
>>> On Tue, Jul 30, 2013 at 12:27 PM, Gary Dale 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:
Re: [Bacula-users] What's wrong with my schedule?
On Tue, Jul 30, 2013 at 2:10 PM, Gary Dale wrote:
> On 30/07/13 12:41 PM, John Drescher wrote:
>> On Tue, Jul 30, 2013 at 12:27 PM, Gary Dale 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: N
Re: [Bacula-users] What's wrong with my schedule?
On 30/07/13 12:41 PM, John Drescher wrote:
> On Tue, Jul 30, 2013 at 12:27 PM, Gary Dale 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-back
Re: [Bacula-users] What's wrong with my schedule?
On Tue, Jul 30, 2013 at 12:27 PM, Gary Dale 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:
Re: [Bacula-users] What's wrong with my schedule?
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
Re: [Bacula-users] What's wrong with my schedule?
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
--
NIONEX --- Ein Unternehmen der Bertelsmann SE & Co. KGaA
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
