Re: [Bacula-users] VirtualFull Jobs
Good morning Kern, So you mean that even you create a virtual full in a different pool there’s no need to later migrating for operational purposes like using it for a restore or a new virtual full?. Do you mean this? Best regards, El 04/05/2014, a las 14:51, Kern Sibbald k...@sibbald.com escribió: Hello, I believe that I have removed the restriction on using a different Pool. Perhaps it is not well documented, in which case if you make it work, as I think a lot of people have done, a patch for the manual would be appreciated. Kern On 04/30/2014 12:45 PM, Egoitz Aurrekoetxea wrote: Good morning, I’m at this moment doing real full jobs of my servers. I have some slowness (in backup) with some servers due to it’s activity. I have tested virtual full jobs and work like a charm :) but I have one problem; normally I schedule a real full job and I’m done… as virtual full jobs have to be done in another pool, later migrated and later a new incremental job should be done (for replacing a normal full) how could I manage for automating this tasks, without starting one before the other one and… basically for automating all this tasks involving a virtual full job but having in mind that this automation has to be in a proper order, if one job fails should not continue with the other “sub jobs” let’s say of the virtual full job?… how do you manage for this tasks? Best regards, -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Backing up Xen virtual machines (LVM)
Hello everyone I am preparing to implement Bacula on one of the servers I look after, but being new to the Bacula subject I would like to ask for some advisory from users more experienced. The server I mean to run Bacula on is Debian Wheezy-based and serves as a host to several LVM-based Xen virtual machines running Wheezy as well. Some of the VMs are database servers (mainly PostgreSQL). The intended Bacula version is 5.2.6, available in Wheezy repositories. My first question concerns where it is more advisable to place Bacula daemons: on the host system (and back up using LVM snapshots) or in the virtual machines themselves? I guess it's easier to ensure data consistency using LVM snapshots but I am afraid it would be much harder to restore the machine in this way so I am inclined to install Bacula in the VMs. However, wisdom comes from experience, so I ask you, the more seasoned users: which of the ways is less likely to give me headaches and what are possible 'gotchas' in each one? My intended use of Bacula is being able to restore a failed VM back up quickly in case of a disaster, rather than restoring single files. Any recommendations would be more than welcome. Best regards, Dawid Piotrowski -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] staus dir in bconsole during attr spooling usually hangs bacula
crml-bu-l-00-dir Version: 5.2.5 (26 January 2012) i686-pc-linux-gnu ubuntu 12.04 Has anyone else encountered this? I have been able to get my full backups to complete if I leave bconsole alone. I have one backup that backs up ~150Gb of over 11 Million small files and the attribute list takes many hours to complete. I'd like to be able to check the status of the other backups that have occurred just before the big one without it hanging every time. Status client does not affect bconsole (I presume because it queries the client FD and not the DB). But any other status command hangs bacula/bconsole. Regards, Larry Rosen Linux Administrator Digonex Technologies Inc. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up Xen virtual machines (LVM)
On 5/5/2014 10:44 AM, Dawid Piotrowski wrote: Hello everyone I am preparing to implement Bacula on one of the servers I look after, but being new to the Bacula subject I would like to ask for some advisory from users more experienced. The server I mean to run Bacula on is Debian Wheezy-based and serves as a host to several LVM-based Xen virtual machines running Wheezy as well. Some of the VMs are database servers (mainly PostgreSQL). The intended Bacula version is 5.2.6, available in Wheezy repositories. My first question concerns where it is more advisable to place Bacula daemons: on the host system (and back up using LVM snapshots) or in the virtual machines themselves? I guess it's easier to ensure data consistency using LVM snapshots but I am afraid it would be much harder to restore the machine in this way so I am inclined to install Bacula in the VMs. However, wisdom comes from experience, so I ask you, the more seasoned users: which of the ways is less likely to give me headaches and what are possible 'gotchas' in each one? My intended use of Bacula is being able to restore a failed VM back up quickly in case of a disaster, rather than restoring single files. Any recommendations would be more than welcome. Keep in mind that creating a LVM snapshot of an active filesystem is never a valid strategy. For example, DB tables must be locked while the LVM snapshot is created. It only takes a brief time to create the snapshot, but the VM must somehow be made quiescent while the snapshot is created. The only safe way I'm aware of is to pause the VM, create the snapshot, then resume the VM. Once created, the snapshot will have to store copies of modified blocks for as long as it lives, (ie. until it is backed up with Bacula). This means you must make sure volume groups have sufficient unallocated space for the needed snapshots. Nevertheless, Bacula jobs can be configured to run scripts before and after the backup so the LVM snapshot creation can be automated. That said, both methods are useful in different ways. LVM snapshots are great for disaster recovery or anything where restore can be an all-or-nothing process. On the other hand, for a file server VM where there is a need to restore that single file that a user accidentally deleted, LVM snapshots require more admin intervention. After restoring the snapshot it has to be mounted and the requested file found and somehow copied over to the VM. With bacula-fd running on the VM, restoring a subset of files/directories is easier and more fire-and-forget, because all that need be done is start the restore from the Bacula console. I recommend installing bacula-fd on file server VMs and using LVM snapshots for other VMs. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] staus dir in bconsole during attr spooling usually hangs bacula
Hello, I suspect that your database is not really well tuned, and is probably MySQL. In the Bacula version you are running, if you do commands that interact with the database, bconsole can block a very long time, but I have never heard of Bacula/bconsole blocking. In any case, even with a poorly tuned database if you upgrade to 7.0.x, you probably will not experience this problem since we have made several performance improvements in just the case you are reporting. Best regards, Kern On 05/05/2014 05:27 PM, Larry A. Rosen wrote: crml-bu-l-00-dir Version: 5.2.5 (26 January 2012) i686-pc-linux-gnu ubuntu 12.04 Has anyone else encountered this? I have been able to get my full backups to complete if I leave bconsole alone. I have one backup that backs up ~150Gb of over 11 Million small files and the attribute list takes many hours to complete. I'd like to be able to check the status of the other backups that have occurred just before the big one without it hanging every time. Status client does not affect bconsole (I presume because it queries the client FD and not the DB). But any other status command hangs bacula/bconsole. Regards, Larry Rosen Linux Administrator Digonex Technologies Inc. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Fatal error: askdir.c:340 NULL Volume name. This shouldn't happen!!!
Hello, I believe this bug is present in version 7.0.3. I just had it happen last night, much like I saw about 2 years ago. I run 100s of incrementals each night across 2 LTO tap drives, running with a concurrency limit, so that jobs start whenever others are finished (i.e. I cannot stagger their start times.). I'm assuming this is again a race condition, but one as an end-user I really cannot workaround. So far the problem is not frequent, but does still appear to be an issue. thanks, Stephen On 02/20/2014 09:30 AM, Kern Sibbald wrote: Hello Wolfgang, The drive is allocated first. Your analysis is correct, but obviously something is wrong. I don't think this is happening any more with the Enterprise version, so it will very likely be fixed in the next release as we will backport (or flowback) some rather massive changes we have made in the last during the freeze to the community version. If you want to see what is going on a little more, turn on a debug level in the SD of about 100. Likewise you can set a debug level in the SD of say 1 or 2, then when you do a status, if Bacula is having difficulties reserving a drive, it will print out more detailed information on what is going on -- this last is most effective if jobs end up waiting because a resource (drive or volume) is not available. Best regards, Kern On 02/17/2014 11:54 PM, Wolfgang Denk wrote: Dear Kern Sibbald, In message 5301db23.6010...@sibbald.com you wrote: Were you careful to change the actual volume retention period in the catalog entry for the volume? That requires a manual step after changing the conf file. You can check two ways: Yes, I was. list volumes shows the new retention period for all volumes. 1. Look at the full output from all the jobs and see if any volumes were recycled while the batch of jobs ran. Not in this run, and not in any of the last 15 or so before that. 2. Do a llist on all the volumes that were used during the period the problem happened and see if they were freshly recycled and that the retention period is set to your new value. retention period is as expected, no recycling happened. In any case, I will look over your previous emails to see if I see anything that could point to a problem, and I will look at the bug report, but without a test case, this is one of those nightmare bugs that take huge resources and time to fix. Hm... I wonder why the DIR allocates for two simultaneous running jobs two pairs of (DRIVE, VOLUME), but not using the volume currently mounted in the respective drive, but in the other one. I would expect, that when a job starts, that either a volume or a drive is selected first: - if the drive is selected first, and it has a tape loaded which is in the right pool, and in status append, then there should be no need to ask for any other tape. - if the volume is allocated first, and it is already loaded in a suitable drive, then that drive should be used, ant not the other one. Best regards, Wolfgang Denk -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 510.664.9177 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] No log output from prune expired and truncate commands
On 2014-05-05 00:41, Kern Sibbald wrote:
On 04/25/2014 10:07 PM, Brady, Mike wrote:
On 2014-04-25 11:13, Brady, Mike wrote:
On 2014-04-25 09:17, Kern Sibbald wrote:
On 04/24/2014 10:37 PM, Brady, Mike wrote:
On 2014-04-25 07:59, Brady, Mike wrote:
I am doing some testing with Bacula 7 and amongst other things am
looking at the prune expired and truncate console commands.
I have added the following runscript to the BackupCatalog job
RunScript {
RunsWhen=Before
RunsOnClient=No
Console = prune expired volume yes
Console = truncate allpools storage=FileStorage01
}
This appears to be working in that the appropriate volumes are
being
truncated when they should be, but all I see in the log is
25-Apr 00:10 bacula03-dir JobId 12490: console command: run
BeforeJob
prune expired volume yes
25-Apr 00:10 bacula03-dir JobId 12490: console command: run
BeforeJob
truncate allpools storage=FileStorage01
When I run these commands in bconsole there is always output.
Even
if
it is just to say that there are no volumes to truncate, so I had
expected to see this output in the log under JobId 0. Is console
command
output no logger logged from runscripts or am I missing something?
Thanks
Mike
I just got the 3 days worth of JobId 0 log entries in the log in
one
go,
including all the output I had expected from the prune expired and
truncate commands.
23-Apr 06:58 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
23-Apr 06:58 bacula03-dir JobId 0: Using Catalog MyCatalog
23-Apr 06:58 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
23-Apr 06:58 bacula03-dir JobId 0: Using Catalog MyCatalog
23-Apr 06:58 bacula03-dir JobId 0: No Volumes found to perform
truncate
action.
23-Apr 06:58 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
23-Apr 06:58 bacula03-dir JobId 0: Using Catalog MyCatalog
23-Apr 06:58 bacula03-dir JobId 0: No Volumes found to perform
truncate
action.
24-Apr 00:10 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
24-Apr 00:10 bacula03-dir JobId 0: Using Catalog MyCatalog
24-Apr 00:10 bacula03-dir JobId 0: The current Volume
IncPool-0109
retention period is: 14 days
24-Apr 00:10 bacula03-dir JobId 0: There are no more Jobs
associated
with Volume IncPool-0109. Marking it purged.
24-Apr 00:10 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
24-Apr 00:10 bacula03-dir JobId 0: Using Catalog MyCatalog
24-Apr 00:10 bacula03-dir JobId 0: Connecting to Storage daemon
FileStorage01 at 192.168.42.45:9103 ...
24-Apr 00:10 bacula03-dir JobId 0: 3000 OK label. VolBytes=212
DVD=0
Volume=IncPool-0109 Device=FileDevice01
(/bacula_storage/FileDevice)
24-Apr 00:10 bacula03-dir JobId 0: The volume IncPool-0109 has
been
truncated
24-Apr 00:10 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
24-Apr 00:10 bacula03-dir JobId 0: Using Catalog MyCatalog
24-Apr 00:10 bacula03-dir JobId 0: No Volumes found to perform
truncate
action.
25-Apr 00:10 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
25-Apr 00:10 bacula03-dir JobId 0: Using Catalog MyCatalog
25-Apr 00:10 bacula03-dir JobId 0: The current Volume
CatalogBackup0344 retention period is: 14 days
25-Apr 00:10 bacula03-dir JobId 0: There are no more Jobs
associated
with Volume CatalogBackup0344. Marking it purged.
25-Apr 00:10 bacula03-dir JobId 0: The current Volume
CatalogBackup0242 retention period is: 14 days
25-Apr 00:10 bacula03-dir JobId 0: There are no more Jobs
associated
with Volume CatalogBackup0242. Marking it purged.
25-Apr 00:10 bacula03-dir JobId 0: The current Volume
CatalogBackup0241 retention period is: 14 days
25-Apr 00:10 bacula03-dir JobId 0: There are no more Jobs
associated
with Volume CatalogBackup0241. Marking it purged.
25-Apr 00:10 bacula03-dir JobId 0: The current Volume
IncPool-0128
retention period is: 14 days
25-Apr 00:10 bacula03-dir JobId 0: There are no more Jobs
associated
with Volume IncPool-0128. Marking it purged.
25-Apr 00:10 bacula03-dir JobId 0: Automatically selected Catalog:
MyCatalog
25-Apr 00:10 bacula03-dir JobId 0: Using Catalog MyCatalog
25-Apr 00:10 bacula03-dir JobId 0: Connecting to Storage daemon
FileStorage01 at 192.168.42.45:9103 ...
25-Apr 00:10 bacula03-dir JobId 0: 3000 OK label. VolBytes=217
DVD=0
Volume=CatalogBackup0344 Device=FileDevice01
(/bacula_storage/FileDevice)
25-Apr 00:10 bacula03-dir JobId 0: The volume CatalogBackup0344
has
been truncated
25-Apr 00:10 bacula03-dir JobId 0: 3000 OK label. VolBytes=217
DVD=0
Volume=CatalogBackup0241 Device=FileDevice01
(/bacula_storage/FileDevice)
25-Apr 00:10 bacula03-dir JobId 0: The volume CatalogBackup0241
has
been truncated
25-Apr 00:10 bacula03-dir JobId 0: 3000 OK label. VolBytes=217
DVD=0
Volume=CatalogBackup0242 Device=FileDevice01
(/bacula_storage/FileDevice)
25-Apr 00:10 bacula03-dir
