I'm experiencing a critical problem where tape labels on volumes with data
get corrupted, leaving all data on the tape inaccessible to bacula.
I'm running bacula 5.2.2 built from source, under Linux (CentOS 5.7
x86_64).
This problem has happened with approximately 15 tapes over approximately 6
mo
On Mon, Jan 23, 2012 at 6:08 PM, Nikola Lazic wrote:
> I have Bacula 5.0.3 on FreeBSD 8.2 backing up to an IBM Ultrium ULT3580 tape
> drive, using 400~800GB tapes, connected to an Adaptec 39320LPE Ultra320 SCSI
> adapter. I'm using SQLite and have 4GB of RAM.
>
> I used to have a Quantum DLTV4 tap
I have Bacula 5.0.3 on FreeBSD 8.2 backing up to an IBM Ultrium ULT3580 tape
drive, using 400~800GB tapes, connected to an Adaptec 39320LPE Ultra320 SCSI
adapter. I'm using SQLite and have 4GB of RAM.
I used to have a Quantum DLTV4 tape drive, but I was getting SCSI errors
every few weeks, so I sw
> But will this speed up my backups? Generally speaking, should Bacula be
> able to write two the two tapes devices more quickly than it can write
> to one? The unit in question is a Tandberg Data StorageLibrary T24 LTO
> with two serial attached scsi LTO4 tape devices, attached to a server
> ru
Hi everybody,
We have been using Bacula 5.0.3 for a while with a setup that includes
one tape library with one LTO3 device.
We have upgraded to a new autochanger with two LTO4 devices. I'm hoping
to make maximum use of the second drive. But I have a question
regarding speed.
Here is our backup
1: Make sure you have enough ram in your mysql box (ie, several 10s of Gb)
2: Make sure you tune mysql properly. Most of the supplied config
examples are for sub-1Gb memory configuration.
3: Make sure you have the _correct_ indexes built. this is in the bacula
knowledgebase.
4: For systems wi
On 01/23/2012 10:28 AM, Uwe Schuerkamp wrote:
> I've run mysqltuner on the db a couple of times as this isn't the
> first time we've had problems during a restore, and it looks ok (to my
> untrained, non-dba eyes anyway):
>
> ##
>
Hi folks,
we're running four bacula installations, most of them on version 5.0.x
compiled from source on CentOS 5.x / 6.x 64bit servers. We're mostly
happy with the setup, backups are fast, reliable and generally do not
cause us a lot of headaches.
Today, a colleague asked me to restore some dat
Dear Eric
Thanks for the clue regarding queries.
I have just looked at the default set of queries I use
(examples/sample-query.sql) and noticed statements like
# 5
:List all backups for a Client
*Enter Client Name:
SELECT DISTINCT Job.JobId as JobId,Client.Name as Client,
FileSet.FileSet AS
please have a look at the readme file at:
http://repos.fedorapeople.org/repos/slaanesh/bacula/README.txt
there's this note:
** The included /usr/share/doc/bacula-common-%{version}/README.Fedora contains
quick installation instructions and notes **
You'll find your quick answer by reading it.
Hello Stephen,
On 23/01/2012 09:08, Stephen G Carr wrote:
> Dear All
>
> Have anyone had similar problems with 5.2.4 with backup warnings - the
> MAJOR problem seems that the Backup is NOT added to the catalog and as I
> backup clients to disc and migrate full backups to tape I suspect these
> job
Dear All
Has anyone had similar problems with 5.2.4 with backup warnings.
The MAJOR problem seems that the Backup is NOT added to the catalog and
as I backup clients to disc volume and then migrate Full backups to tape
I suspect these jobs will not be migrated - the migration jobs will run
ton
Hello,
please have a look at the readme file at:
http://repos.fedorapeople.org/repos/slaanesh/bacula/README.txt
there's this note:
** The included /usr/share/doc/bacula-common-%{version}/README.Fedora contains
quick installation instructions and notes **
You'll find your quick answer by readin
Dear All
Have anyone had similar problems with 5.2.4 with backup warnings - the
MAJOR problem seems that the Backup is NOT added to the catalog and as I
backup clients to disc and migrate full backups to tape I suspect these
jobs will not be migrated - the jobs migration jobs run tonight.
I
14 matches
Mail list logo