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=49501711iu=/4140/ostg.clktrk
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Is Truncate just broken?
Dear Kern, Thanks for the explanation. I'll have to dig deeper on my end to see what else could be at the root of the issue. As explained, my disk volumes are on ZFS, but again this should not be an issue and was working for me previously. Sincerely, Shon On Wed, Jul 24, 2013 at 3:35 PM, Kern Sibbald k...@sibbald.com wrote: Hello, ftruncate did not seem to work over NFS or at least on certain versions, so I implemented code that if after doing an ftruncate, the file size (via an fstat) is non-zero, Bacula will delete and recreate the Volume. This is not ideal, because it may create it with different permissions and/or owner, group but it seemed to work. If you drop the SD's user from root to bacula, depending on how you have defined your NFS volume permissions, the SD may be unable do the delete and recreate. Nothing has changed in that code for many years. Best regards, Kern On 07/22/2013 04:06 PM, Mingus Dew wrote: Thanks for the reply. Specifically I'm using Bacula 5.2.13 on Solaris 10 x86. My disk backups are stored on ZFS. I saw some old threads about truncate not working right on NFS but then some code changes were made that actually deleted, then recreated the volume instead of using ftruncate. I know this used to work for me, but doesn't seem to anymore. I'm wondering if something happened in more recent Bacula versions that changed this again. * * Yours, Shon* * On Fri, Jul 12, 2013 at 3:53 AM, Radosław Korzeniewski rados...@korzeniewski.net wrote: Hello, 2013/7/11 Mingus Dew shon.steph...@gmail.com I don't think I've ever gotten it to work under any circumstance, either manually or automated. It is working fine, automatic or manually. I use it on a lot of Bacula deployments without problems. best regards -- Radosław Korzeniewski rados...@korzeniewski.net -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today!http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Bacula-users mailing listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users -- 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=49501711iu=/4140/ostg.clktrk___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Is Truncate just broken?
Hello Shon Well, maybe the Solaris NFS has additional quirks that we have not yet identified. In any case, we have not changed the code concerning file truncation for quite a few years as far as I can remember. Good luck on finding the problem(s) ... Kern On 07/30/2013 01:41 PM, Mingus Dew wrote: Dear Kern, Thanks for the explanation. I'll have to dig deeper on my end to see what else could be at the root of the issue. As explained, my disk volumes are on ZFS, but again this should not be an issue and was working for me previously. Sincerely, Shon On Wed, Jul 24, 2013 at 3:35 PM, Kern Sibbald k...@sibbald.com mailto:k...@sibbald.com wrote: Hello, ftruncate did not seem to work over NFS or at least on certain versions, so I implemented code that if after doing an ftruncate, the file size (via an fstat) is non-zero, Bacula will delete and recreate the Volume. This is not ideal, because it may create it with different permissions and/or owner, group but it seemed to work. If you drop the SD's user from root to bacula, depending on how you have defined your NFS volume permissions, the SD may be unable do the delete and recreate. Nothing has changed in that code for many years. Best regards, Kern On 07/22/2013 04:06 PM, Mingus Dew wrote: Thanks for the reply. Specifically I'm using Bacula 5.2.13 on Solaris 10 x86. My disk backups are stored on ZFS. I saw some old threads about truncate not working right on NFS but then some code changes were made that actually deleted, then recreated the volume instead of using ftruncate. I know this used to work for me, but doesn't seem to anymore. I'm wondering if something happened in more recent Bacula versions that changed this again. * * Yours, Shon** On Fri, Jul 12, 2013 at 3:53 AM, Radosław Korzeniewski rados...@korzeniewski.net mailto:rados...@korzeniewski.net wrote: Hello, 2013/7/11 Mingus Dew shon.steph...@gmail.com mailto:shon.steph...@gmail.com I don't think I've ever gotten it to work under any circumstance, either manually or automated. It is working fine, automatic or manually. I use it on a lot of Bacula deployments without problems. best regards -- Radosław Korzeniewski rados...@korzeniewski.net mailto:rados...@korzeniewski.net -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net mailto:Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- 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=49501711iu=/4140/ostg.clktrk___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula-dir run failure on Ubuntu 12.04.02
Hi folks, I'm trying to build and run Bacula 5.2.13 on Ubuntu server 12.04.02. I have downloaded source and bacula builds with no problem but the director fails to start with the following error: node1:~# /opt/bacula/bin/bacula-dir -f /opt/bacula/bin/bacula-dir: symbol lookup error: /opt/bacula/lib/libbaccats-5.2.13.so: undefined symbol: mysql_thread_safe node1:~# dpkg --list |grep libmysqlclient ii libmysqlclient-dev 5.5.32-0ubuntu0.12.04.1 MySQL database development files ii libmysqlclient18 5.5.32-0ubuntu0.12.04.1 MySQL database client library node1:~# I went back and double checked my configure and make output and all looks good. checking for mysql_thread_safe in -lmysqlclient_r... yes checking for pthread_create in -lpthread... yes ... C Compiler: gcc 4.6.3-1ubuntu5) C++ Compiler: /usr/bin/g++ 4.6.3-1ubuntu5) Compiler flags:-g -O2 -Wall -fno-strict-aliasing -fno-exceptions -fno-rtti Linker flags: Libraries:-lpthread -ldl -ldl ... Making libbaccats-mysql.la ... /home/mrc/bacula-build/bacula-5.2.13/libtool --silent --tag=CXX --mode=link /usr/bin/g++ -D_BDB_PRIV_INTERFACE_ -o libbaccats-mysql.la mysql.lo -export-dynamic -rpath /opt/bacula/lib -release 5.2.13 \ -soname libbaccats-5.2.13.so Make of sqllibs is good ... /home/mrc/bacula-build/bacula-5.2.13/libtool --silent --tag=CXX --mode=link /usr/bin/g++ -L../lib -L../cats -L../findlib -o bacula-dir dird.o admin.o authenticate.o autoprune.o backup.o bsr.o catreq.o dir_plugins.o dird_conf.o expand.o fd_cmds.o getmsg.o inc_conf.o job.o jobq.o migrate.o mountreq.o msgchan.o next_vol.o newvol.o pythondir.o recycle.o restore.o run_conf.o scheduler.o ua_acl.o ua_cmds.o ua_dotcmds.o ua_query.o ua_input.o ua_label.o ua_output.o ua_prune.o ua_purge.o ua_restore.o ua_run.o ua_select.o ua_server.o ua_status.o ua_tree.o ua_update.o vbackup.o verify.o \ -lbacfind -lbacsql -lbaccats -lbacpy -lbaccfg -lbac -lm -lpthread -ldl -ldl \ Make of dird is good I'm fairly experienced running and building Bacula on Ubuntu server going back to the 3.x days and Ubuntu 8.04 but I'm not really a programmer, realy more of an admin that knows how to use google and follow instructions and just enough programming to get myself into trouble. I can't figure this one out. Anyone have any ideas? My ./configure file is the example from the 5.2.13 ReleaseNotes minus the --enable-bat because I don't have Qt loaded. Is this more of a question for the bacula-devel list? Any help or ideas are greatly appreciated. Thanks, Mike -- 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=49501711iu=/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 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
Re: [Bacula-users] What's wrong with my schedule?
On Tue, Jul 30, 2013 at 12:27 PM, Gary Dale garyd...@torfree.net 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
[Bacula-users] HEADS UP: change to FreeBSD port coming
This affects only FreeBSD users. At present, when upgrading sysutils/bacula-server or sysutils/bacula-client, the port/package will stop bacula-dir bacula-sd (or bacula-fd respectively). This is done as part of the uninstall before doing the subsequent install. I think this is not the ideal thing to do. Here are two example scenarios under the current situation: 1 - when you're upgrading several servers, you get monitoring systems telling you that the process has stopped running… annoying 2 - when you upgrading in a FreeBSD jail *HOST*, the current approach will also stop the corresponding processes in any jails #1 is annoying. #2 is downright unexpected. I propose that we don't stop the processes at all. Leave it up to the sysadmin to do the right thing. They can decide to: portupgrade restart or stop portupgrade start But this change gives them the choice. Please discuss. -- Dan Langille - http://langille.org -- 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=49501711iu=/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 12:41 PM, John Drescher wrote:
On Tue, Jul 30, 2013 at 12:27 PM, Gary Dalegaryd...@torfree.net 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
Re: [Bacula-users] What's wrong with my schedule?
On Tue, Jul 30, 2013 at 2:10 PM, Gary Dale garyd...@torfree.net wrote:
On 30/07/13 12:41 PM, John Drescher wrote:
On Tue, Jul 30, 2013 at 12:27 PM, Gary Dalegaryd...@torfree.net 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
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 Dalegaryd...@torfree.net wrote:
On 30/07/13 12:41 PM, John Drescher wrote:
On Tue, Jul 30, 2013 at 12:27 PM, Gary Dalegaryd...@torfree.net 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:
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 Dalegaryd...@torfree.net wrote:
On 30/07/13 12:41 PM, John Drescher wrote:
On Tue, Jul 30, 2013 at 12:27 PM, Gary Dalegaryd...@torfree.netwrote:
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 FullDifferential 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
