On 06/21/2011 08:06 PM, Dan Langille wrote:
>
> On Jun 21, 2011, at 3:59 AM, Marcus Mülbüsch wrote:
>
>> I want to migrate my bacula installation from mysql to postgresql,
>> following the guide in
>> http://www.bacula.org/5.0.x-manuals/en/main/main/Installing_Configuring_Post.html#SECTION00445
On 21/06/2011 14:20, John Drescher wrote:
I believe the only way that can happen (if you are in the correct tape
density mode)
I found something strange. If I try to issue this command:
mt -f /dev/nst0 status
I'll get one line that says:
On 06/21/11 22:06, Dan Langille wrote:
>
> On Jun 21, 2011, at 3:59 AM, Marcus Mülbüsch wrote:
>
>> I want to migrate my bacula installation from mysql to postgresql,
>> following the guide in
>> http://www.bacula.org/5.0.x-manuals/en/main/main/Installing_Configuring_Post.html#SECTION004450
On Jun 21, 2011, at 3:59 AM, Marcus Mülbüsch wrote:
> I want to migrate my bacula installation from mysql to postgresql,
> following the guide in
> http://www.bacula.org/5.0.x-manuals/en/main/main/Installing_Configuring_Post.html#SECTION00445
>
> After dumping and converting th
>> No difference at all.
>
> So why are both, at the evidence, acting differently?
>
I do not know.
>
>>> >
>>> > II'll try to force the maximum size of the tape in the config but I
>>> > would
>>> > have to put it over 80GB limit if I only want the hardware compression
>>> > to be useful. Not s
On 21/06/2011 20:57, John Drescher wrote:
>> So, since btape comes from Bacula, I assume that, in some way, Bacula
>> > should be able to write to my VXA-2 tape a more or less 80GB of data. So
>> > what's the difference between bacula-sd's way of accessing the tape and
>> > btape's way?
>> >
> N
> So, since btape comes from Bacula, I assume that, in some way, Bacula
> should be able to write to my VXA-2 tape a more or less 80GB of data. So
> what's the difference between bacula-sd's way of accessing the tape and
> btape's way?
>
No difference at all.
>
> II'll try to force the maximum si
On 21/06/2011 19:33, ganiuszka wrote:
> You can use vxaTool to diagnostic purpose for your tape drive. There
> is option (from vxaTool readme file):
>
> -t [W/R/F] (optional)
> Test write/read functionality of the device.
>
> Optional [R]ead-only, [W]rite-only and [F]ull-tape flags
> **
2011/6/21 Christian Tardif :
> Hi,
>
> I have a VXA-2 tape used with X23 tapes (replacement for V23 tapes)
> that should backup 80GB Uncompressed. Bacula stops after an average of
> 27GB, stating that the media is full. It seems that tapeinfo thinks
> that it has 80GB available (see below).
>
> H
Hello All,
I am trying to use the Python scripting facility in Bacula.
An initial test (in the JobEvents class per the DirStartup.py
example file distributed with Bacula)...
def NewVolume(self, job):
job.JobReport = "Python: in NewLabel method (1)"
job.JobReport = "Python: in NewLabe
On Tue, Jun 21, 2011 at 2:11 PM, Christian Tardif
wrote:
>
> On 21/06/2011 13:01, John Drescher wrote:
>
> Look for scsi errors in your dmesg. Bacula will assume it hits the end
> of the tape when it hits any write error.
>
> Don't have any SCSI error on dmesg. It really looks like Bacula thinks t
On 21/06/2011 13:01, John Drescher wrote:
Look for scsi errors in your dmesg. Bacula will assume it hits the end
of the tape when it hits any write error.
Don't have any SCSI error on dmesg. It really looks like Bacula
thinks that it can only write 30GB of
On 06/20/2011 12:39 PM, Martin Simmons wrote:
>> On Mon, 20 Jun 2011 11:13:39 -0600, Stuart McGraw said:
>>
>> > If you also wish to exclude other dot-directories, I would try something
>> > like:
>> >
>> > FileSet
>> > {
>> >Include
>> >{
>> > Options
>> > {
>> >
On Tue, Jun 21, 2011 at 12:48 PM, Christian Tardif
wrote:
> Hi,
>
> I have a VXA-2 tape used with X23 tapes (replacement for V23 tapes)
> that should backup 80GB Uncompressed. Bacula stops after an average of
> 27GB, stating that the media is full. It seems that tapeinfo thinks
> that it has 80G
Hi,
I have a VXA-2 tape used with X23 tapes (replacement for V23 tapes)
that should backup 80GB Uncompressed. Bacula stops after an average of
27GB, stating that the media is full. It seems that tapeinfo thinks
that it has 80GB available (see below).
How can I fix this in Bacula in order to
verson for dir, sd, fd: 5.0.2
platform: ubuntu 32bit 10.10
dir,sd, fd are in same server
trying to restore:
bconsole -> run -> RestoreFiles ->
Run Restore job
JobName:RestoreFiles
Bootstrap: *None*
Where: /tmp/bacula-restore
Replace: always
Client: ubuntu10x32-test-fd
S
Director {# define myself
Name = ubuntu10x32-test-dir
DIRport = 9101# where we listen for UA connections
QueryFile = "/etc/bacula/scripts/query.sql"
WorkingDirectory = "/var/lib/bacula"
PidDirectory = "/var/run/bacula"
Maximum Concurrent Jobs
At about 80GB of a ~300GB job the Bacula File Daemon v5.0.3 on a MAC OSX
10.5.8 PPC server died and of course the backup failed.
I have been running Bacula for several years on Linux, Mac, Windows and
FreeBSD and have never seen the File Daemon die like this so I thought it
might make sense to pos
On 06/20/2011 08:45 PM, Craig Van Tassle wrote:
> I was wondering if anyone knew how to make a Rescue CD/USB key for
> Debian?
Hi,
I just build an Bacula USB recue system with SSL support from an up to
date Ubuntu 11.04. It offers a 4GB non volatile disk on which you can
install all necessary p
I want to migrate my bacula installation from mysql to postgresql,
following the guide in
http://www.bacula.org/5.0.x-manuals/en/main/main/Installing_Configuring_Post.html#SECTION00445
After dumping and converting the database the sql-file now has 9GiB.
I began loading the db in
20 matches
Mail list logo
