[Bacula-users] How Label Format count volumes?

2007-11-15 Thread Alejandro Alfonso
Hello! I'm upgrading my old bacula instalations to bacula 2.2.x After some tries, i have a doubt about automatic label of File Devices Using LabelMedia = yes in Device, and Label Format = Server-, in Pool section, label suffix starts counting in sum of existing Volumes in ALL Pools (example: 2

Re: [Bacula-users] Backup catalog not running.

2007-11-15 Thread Cedric Devillers
Cedric Devillers wrote: Arno Lehmann wrote: Hi, 13.11.2007 12:54,, Cedric Devillers wrote:: Hello, I have a little problem with one of our bacula installation. Let me explain the setup first. There is two server, the first has the data and the storage daemon (meia). The second is the

[Bacula-users] SunStorageTek C2

2007-11-15 Thread Kazon, Krzysztof Maciej
Hi everybody, Whether somebody had experience in use: Autoloader: http://www.sun.com/storagetek/tape_storage/tape_libraries/c2/ http://www.sun.com/storagetek/tape_storage/tape_libraries/c2/ OS: Solaris 10 Tape: LTO3 Whether somebody knows, whether autoloader will work? I must create

[Bacula-users] bconsole Director authorization problem and tapes put into read error (LTO4)

2007-11-15 Thread Win Htin
Hi Folks, Just as I thought I'm ready for prime time, I'm back to square one with TWO unexpected issues that popped up. # *bconsole Director authorization problem: *After upgrading to 2.2.6 I noticed I get failures time to time when I issue the bconsole command. Following is what I see from my

[Bacula-users] full/incremental and predefined changer slots?

2007-11-15 Thread Kristian Rink
Folks; currently into reorganizing the tape-backup of some of our systems using bacula, I do have a situation like this: - Backups go to tapes, full backup needs to span across two tapes, incrementals fit on one. - We do use a Tandberg LTO-2 tape changer, the tapes for weekend full backup

Re: [Bacula-users] bconsole Director authorization problem and tapes put into read error (LTO4)

2007-11-15 Thread John Drescher
Just as I thought I'm ready for prime time, I'm back to square one with TWO unexpected issues that popped up. # bconsole Director authorization problem: After upgrading to 2.2.6 I noticed I get failures time to time when I issue the bconsole command. Following is what I see from my CLI.

[Bacula-users] Fwd: bconsole Director authorization problem and tapes put into read error (LTO4)

2007-11-15 Thread John Drescher
-- Forwarded message -- From: John Drescher [EMAIL PROTECTED] Date: Nov 15, 2007 11:57 AM Subject: Re: [Bacula-users] bconsole Director authorization problem and tapes put into read error (LTO4) To: Win Htin [EMAIL PROTECTED] On Nov 15, 2007 11:43 AM, Win Htin [EMAIL PROTECTED]

Re: [Bacula-users] 2.2.6 rpm release

2007-11-15 Thread Jeff Dickens
Any idea when the source rpm will be back? I saw that the bad one had been taken down from sf, but there has been no word about its replacement. Scott Barninger wrote: Hello, bacula-2.2.6 has been released to sourceforge. This release should address the RedHat (and clone) issues discussed

Re: [Bacula-users] Fwd: [Bacula-devel] Broken 2.2.6 source rpm in Sourceforge

2007-11-15 Thread Scott Barninger
Hello, Sorry for the delay but I have been out of town until this evening. Not sure what went wrong with the release but I have re-uploaded the srpm now. It should be available now and the file size looks correct. On Tue, 2007-11-13 at 14:10 +0100, Kern Sibbald wrote: Hello Scott, Just to

Re: [Bacula-users] Fwd: [Bacula-devel] Broken 2.2.6 source rpm in Sourceforge

2007-11-15 Thread Jeff Dickens
Thanks. Scott Barninger wrote: Hello, Sorry for the delay but I have been out of town until this evening. Not sure what went wrong with the release but I have re-uploaded the srpm now. It should be available now and the file size looks correct. On Tue, 2007-11-13 at 14:10 +0100, Kern Sibbald

Re: [Bacula-users] Fwd: [Bacula-devel] Broken 2.2.6 source rpm in Sourceforge

2007-11-15 Thread Scott Barninger
No problem. Good thing I don't delete that trusty srpm until I build the next release :-) I hope all is well now. Coming Event Highlights: Per me, will be switching the sqlite package to sqlite3. Per Alan Brown, will be adding a build switch for the mtx package (default off). Hopefully this

Re: [Bacula-users] backup issue with batch table

2007-11-15 Thread Jason Martin
MySQL has its own size limits on files. See: http://wiki.bacula.org/doku.php?id=faq#why_does_mysql_say_my_file_table_is_full -Jason Martin On Thu, Nov 15, 2007 at 05:44:44PM -0600, Nick Jones wrote: Hello, I was hoping someone could help me identify what is going wrong with my backup job?

[Bacula-users] backup issue with batch table

2007-11-15 Thread Nick Jones
Hello, I was hoping someone could help me identify what is going wrong with my backup job? I recently updated from 2.0.3 to 2.2.5 so that building of directory trees for restores were faster (and I am quite pleased). After I updated, everything seemed fine, I was able to run several incremental

[Bacula-users] Volume Size Mismatch: please, help me understand this

2007-11-15 Thread Martin Schmid
Hello Everybody I'm running bacula for quite a while now and also for a quite a high volume on NAS devices. Most of it is running smootly but I do not understand _that_ volume recycling issue: The files are generally limited to 2G in size. From previous backups, the volume Vol_0058 has been

Re: [Bacula-users] backup issue with batch table

2007-11-15 Thread Michael Lewinger
Yups. You could switch to postgres ? Michael On Nov 16, 2007 1:49 AM, Jason Martin [EMAIL PROTECTED] wrote: MySQL has its own size limits on files. See: http://wiki.bacula.org/doku.php?id=faq#why_does_mysql_say_my_file_table_is_full -Jason Martin On Thu, Nov 15, 2007 at 05:44:44PM -0600,

Re: [Bacula-users] backup issue with batch table

2007-11-15 Thread Michael Lewinger
Sorry my mistake: You are using a MyISAM table and the space required for the table exceeds what is allowed by the internal pointer size. MyISAM creates tables to allow up to 4GB by default (256TB as of MySQL 5.0.6), but this limit can be changed up to the maximum allowable size of 65,536TB